Hi David, thank you for sharing your opinion. Could you please clarify your position. You propose to use extensions/options for end-to-end active OAM? Let us look at proactive continuity check between NVEs. Why you think a middlebox needs to be aware of the OAM payload? I believe that a transient NVO3 node should not look into payload if it is not addressed to it at all. Thus I don't agree that the requirement you refer to is applicable to use of active OAM.
Regards, Greg On Mon, Apr 3, 2017 at 11:19 AM, David Mozes <[email protected]> wrote: > Hi , > > I am not supporting the adoption > > I think while the working group decided on Geneve as the encap protocol > > > > This OAM need to be via one of the extensions/options the protocol is > supporting! > > > > This header also violate the number 1 requirements from the > extensions/options > > That node/middlbox don not need to be part of the extensions/ option can > jump directly to the overlay by reading the base header length only > > > > Thx > > David > > > > *From:* nvo3 [mailto:[email protected]] *On Behalf Of *Fioccola > Giuseppe > *Sent:* Monday, April 03, 2017 5:40 PM > *To:* Bocci, Matthew (Nokia - GB) <[email protected]>; NVO3 < > [email protected]>; [email protected] > *Subject:* [nvo3] R: Poll for NVO3 WG adoption and IPR call for > draft-ooamdt-rtgwg-ooam-header-03 > > > > Hi All, > > I have read the draft and support its adoption. > > > > Regards, > > > > Giuseppe > > > > *Da:* nvo3 [mailto:[email protected] <[email protected]>] *Per > conto di *Bocci, Matthew (Nokia - GB) > *Inviato:* venerdì 31 marzo 2017 17:35 > *A:* NVO3; [email protected] > *Oggetto:* [nvo3] Poll for NVO3 WG adoption and IPR call for > draft-ooamdt-rtgwg-ooam-header-03 > > > > This email begins a two week poll for adoption of > draft-ooamdt-rtgwg-ooam-header-03 > in the NVO3 working group. > > > > Please review the draft and send any comments to the NVO3 list. > > Please also indicate whether you support adoption of the draft as an NVO3 > working group document. > > > > Simultaneously, we are also poling for any IPR that may apply to the draft. > > > > Authors and contributors, are you aware of any IPR that applies to this > draft? > > > > If so, has this IPR been disclosed in compliance with IETF IPR rules (see > RFCs 3979, 4879, 3669 and 5378 for more details)? > > > > If you are listed as a document author or contributor, please respond to > > this email stating of whether or not you are aware of any relevant > > IPR. The response needs to be sent to the NVO3 WG mailing list. The > > document will not advance to the next stage until a response > > has been received from each author and each contributor. > > > > This poll closes on Friday 14th April 2017. > > > > Regards > > > > Matthew and Sam > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle > persone indicate. La diffusione, copia o qualsiasi altra azione derivante > dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora > abbiate ricevuto questo documento per errore siete cortesemente pregati di > darne immediata comunicazione al mittente e di provvedere alla sua > distruzione, Grazie. > > *This e-mail and any attachments** is **confidential and may contain > privileged information intended for the addressee(s) only. Dissemination, > copying, printing or use by anybody else is unauthorised. If you are not > the intended recipient, please delete this message and any attachments and > advise the sender by return e-mail, Thanks.* > > *[image: rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail > se non è necessario.* > > >
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
