Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2024-01-10 Thread Jensen Zhang
Hi Zahed, Sorry for the delay. The new revision has been uploaded to resolve your comment: https://datatracker.ietf.org/doc/html/draft-ietf-alto-oam-yang-16 Please let us know if it is enough. Thanks, Jensen On Thu, Dec 14, 2023 at 5:45 PM Zaheduzzaman Sarker < zahed.sarker.i...@gmail.com> wro

Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-12-14 Thread Zaheduzzaman Sarker
Thanks for this Med, I am fine with this inclusion. //Zahed On Wed, Dec 13, 2023 at 10:53 AM wrote: > Hi Zahed, > > > That is understandable, and it this is conscious decision to not cover > > the latest and greatest then I would expect the specification describe > > that. A statement on the cu

Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-12-13 Thread mohamed . boucadair
Hi Zahed, > That is understandable, and it this is conscious decision to not cover > the latest and greatest then I would expect the specification describe > that. A statement on the current scope and the potential extendibility > to cover the new ALTO transport will help here. A PR to clarify t

Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-10-26 Thread mohamed . boucadair
Re-, Please see inline. Cheers, Med > Zahed, > > > > It is a matter of balance between what the WG can successfully deliver vs. > exhaustiveness. Proceeding in steps (having first a base module + including > provision to graft extension) is pragmatic given the limited resources of > the WG. >

Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-10-26 Thread Zaheduzzaman Sarker
On Thu, Oct 26, 2023 at 3:58 PM wrote: > Zahed, > > > > It is a matter of balance between what the WG can successfully deliver vs. > exhaustiveness. Proceeding in steps (having first a base module + including > provision to graft extension) is pragmatic given the limited resources of > the WG. >

Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-10-26 Thread mohamed . boucadair
Zahed, It is a matter of balance between what the WG can successfully deliver vs. exhaustiveness. Proceeding in steps (having first a base module + including provision to graft extension) is pragmatic given the limited resources of the WG. Please note that the spec relies upon common reusable

Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-10-26 Thread Zaheduzzaman Sarker
On Thu, Oct 26, 2023 at 1:19 PM wrote: > Hi Zahed, > > Please see inline. > > Cheers, > Med > > > -Message d'origine- > > De : Zaheduzzaman Sarker via Datatracker > > Envoyé : jeudi 26 octobre 2023 13:12 > > À : The IESG > > Cc : draft-ietf-alto-oam-y...@ietf.org; alto-cha...@ietf.org;

Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-10-26 Thread mohamed . boucadair
Hi Zahed, Please see inline. Cheers, Med > -Message d'origine- > De : Zaheduzzaman Sarker via Datatracker > Envoyé : jeudi 26 octobre 2023 13:12 > À : The IESG > Cc : draft-ietf-alto-oam-y...@ietf.org; alto-cha...@ietf.org; > alto@ietf.org; BOUCADAIR Mohamed INNOV/NET > ; BOUCADAIR M

[alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

2023-10-26 Thread Zaheduzzaman Sarker via Datatracker
Zaheduzzaman Sarker has entered the following ballot position for draft-ietf-alto-oam-yang-15: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to