Re: [sfc] draft-ietf-sfc-oam-packet-00 status & comments (was RE: WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/)

[[e-mail]]

Hi Joel, Franck, 

OK for me. 

See the full candidate changes at: https://tinyurl.com/oam-packet-latest

Cheers,
Med

> -----Message d'origine-----
> De : Joel M. Halpern <[e-mail]>
> Envoyé : jeudi 14 avril 2022 15:56
> À : Frank Brockners (fbrockne) <[e-mail]>; BOUCADAIR
> Mohamed INNOV/NET <[e-mail]>; Greg Mirsky
> <[e-mail]>
> Cc : [e-mail]; Carlos Pignataro (cpignata)
> <[e-mail]>
> Objet : Re: draft-ietf-sfc-oam-packet-00 status & comments (was
> RE: [sfc] WGLC for https://datatracker.ietf.org/doc/draft-ietf-
> sfc-ioam-nsh/)
> 
> Authors, WG participants?  That edit looks acceptable to me?
> Frank, assuming we make that change, are you okay with this being
> sent to the IESG for publication as an RFC?
> 
> Yours,
> Joel
> 
> On 4/14/2022 9:47 AM, Frank Brockners (fbrockne) wrote:
> > Hi Joel,
> >
> > Looking at https://datatracker.ietf.org/wg/sfc/documents/ - it
> does not list draft-ietf-sfc-oam-packet-00 as in last call. The
> WGLC statement got me by surprise - I really missed that.
> >
> > Reading through draft-ietf-sfc-oam-packet-00, the clause that
> Med mentioned earlier could be misread, as in "NSH could interfere
> with the operation of other protocols". Or in other words, the O-
> bit can only be about SFC OAM data, which is what SFC control.
> Otherwise we could go wild and argue for adding additional bits
> like "D-Bit: Packet contains data from a data base" or "C-Bit:
> Packet contains data of the CEO of the company"...
> >
> > Suggested change:
> >
> > OLD:
> >        Such a packet is any NSH-encapsulated packet that
> exclusively includes OAM data.
> >        An OAM data can be included in the Fixed-Length Context
> Header,
> >        optional Context Headers, and/or the inner packet.
> >
> > NEW:
> >        Such a packet is any NSH-encapsulated packet that
> exclusively includes SFC OAM data.
> >        SFC OAM data can be included in the Fixed-Length Context
> Header, optional Context Headers, and/or the inner packet.
> >
> >
> > 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.