Re: [sfc] Robert Wilton's Discuss on draft-ietf-sfc-ioam-nsh-11: (with DISCUSS and COMMENT)

["Frank Brockners (fbrockne)" <[e-mail]>]

Hi Med,


> -----Original Message-----
> From: [e-mail]
> <[e-mail]>
> Sent: Friday, 5 May 2023 09:09
> To: Frank Brockners (fbrockne) <fbrockne=[e-mail]>;
> Rob Wilton (rwilton) <[e-mail]>; The IESG <[e-mail]>
> Cc: [e-mail]; [e-mail]; [e-mail];
> [e-mail]
> Subject: RE: Robert Wilton's Discuss on draft-ietf-sfc-ioam-nsh-11: (with
> DISCUSS and COMMENT)
> 
> Hi Franck, all,
> 
> Please see one comment inline.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : sfc <[e-mail]> De la part de Frank Brockners
> > (fbrockne)
> > Envoyé : jeudi 4 mai 2023 22:21
> > À : Rob Wilton (rwilton) <[e-mail]>; The IESG <[e-mail]>
> > Cc : [e-mail]; [e-mail];
> > [e-mail]; [e-mail] Objet : Re: [sfc] Robert
> > Wilton's Discuss on draft-ietf-sfc-ioam-
> > nsh-11: (with DISCUSS and COMMENT)
> >
> ...
> > >
> > > (3) p 2, sec 3.  IOAM encapsulation with NSH
> > >
> > >      Otherwise
> > >    packets with IOAM are likely to be dropped per [RFC8300].
> > There can
> > >    be multiple IOAM headers added by encapsulating nodes as
> > configured.
> > >
> > > Possibly "MAY" may be better than "can", since RFC 2119 language
> > is
> > > being used elsewhere in this paragraph.
> >
> > ...FB: Changed to MAY in version -12.
> >
> 
> [Med] Isn't this redundant with:
> 
>    Multiple IOAM-Option-Types MAY be included within the NSH
>    encapsulation.

...FB: It is. But does it hurt? If so, I can create another revision and remove the sentence.

Cheers, Frank

> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites
> ou copies sans autorisation. Si vous avez recu ce message par erreur,
> veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes.
> Les messages electroniques etant susceptibles d'alteration, Orange decline
> toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.