Hi Tal,

Thanks for your review.  Please see my responses inline.

Regards,
Ilango

From: Tal Mizrahi [mailto:[email protected]]
Sent: Monday, October 22, 2018 5:42 AM
To: Bocci, Matthew (Nokia - GB) <[email protected]>
Cc: NVO3 <[email protected]>; [email protected]
Subject: Re: [nvo3] Working Group Last Call and IPR Poll for 
draft-ietf-nvo3-geneve-08.txt


Hi,



A couple of comments:



1.          I want to thank the authors for addressing the comments about the 
Security Considerations section of the previous version of the draft.



<Ilango> Glad to know that the new version addresses your previous comments on 
security considerations section.



2.       Regarding the IANA Considerations section:

a.       [RFC5226] was obsoleted by [RFC8126].



<Ilango> We will update the reference to [RFC8126]



b.       I believe that requiring “IETF Review” is too stringent; “Expert 
Review” would make more sense in my opinion.

 <Ilango>  We don’t see a good reason to change this policy. Only the range 
0x00-0xFF is reserved for standardized options under IETF Review. We already 
have a large range (0x0100- 0xFFEF) that is available under a very lenient 
policy (First Come First Served),  so it is hard to see the overall policy as 
being too stringent.

Therefore, I would suggest the following change:

OLD:

The identifiers 0x0-0xFF are to be reserved for standardized options for 
allocation by IETF Review [RFC5226]

NEW:

The identifiers 0x0-0xFF are to be allocated by Expert Review, according to 
Section 4.5 of [RFC8126]

Cheers,
Tal.

On Tue, Oct 9, 2018, 12:08 Bocci, Matthew (Nokia - GB) 
<[email protected]<mailto:[email protected]>> wrote:
This email begins a two-week working group last call for 
draft-ietf-nvo3-geneve-08.txt.
Please review the draft and post any comments to the NVO3 working group list. 
If you have read the latest version of the draft but have no comments and 
believe it is ready for publication as a standards track RFC, please also 
indicate so to the WG email list.

We are also polling for knowledge of any undisclosed IPR that applies to this 
document, to ensure that IPR has been disclosed in compliance with IETF IPR 
rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
If you are listed as an Author or a Contributor of this document, please 
respond to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR. The Document won't progress without answers from all the 
Authors and Contributors.
Currently there are two IPR disclosures against this document.
If you are not listed as an Author or a Contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

This poll will run until Friday 26th October.

Regards

Matthew and Sam
_______________________________________________
nvo3 mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to