Thanks Ali. FYI -- the issue with 802 references pointed out by Luc Andre does not appear to have been fixed in the new version.
On Wed, Jul 23, 2025 at 7:22 PM Ali Sajassi (sajassi) <[email protected]> wrote: > Hi Anoop, > > > > Thanks for pointing out the nits. I took care of them. See below .. > > > > *From: *Anoop Ghanwani <[email protected]> > *Date: *Friday, June 20, 2025 at 10:50 PM > *To: *Ali Sajassi (sajassi) <[email protected]> > *Cc: *Luc André Burdet <[email protected]>, Matthew Bocci (Nokia) < > [email protected]>, NVO3 <[email protected]>, > [email protected] <[email protected]>, > nvo3-chairs <[email protected]> > *Subject: *Re: [nvo3] Re: WG Last Call for draft-ietf-nvo3-rfc7348bis-00 > > I support the document for publication as an RFC. > > > > A few editorial nits (in addition to the ones below): > > > > - It looks like the new text uses "VxLAN". Should probably stick with > "VXLAN" for consistency. > > Ali> done > > > > - Expand VXLAN only once, the very first time. > > Ali> done > > > > - For consistency with the rest of the doc, should probably capitalize > "Section" when referring to section numbers in Section 1. > > Ali> done > > > > - In Section 4.2, there appears to be a spurious line break in the middle > of the 3rd paragraph. > > Ali> removed but it was also in the RFC! > > > > - There seem to be several spurious line breaks in Section 5. > > Ali> removed > > > > Cheers, > > Ali > > > > On Mon, Jun 9, 2025 at 11:37 AM Ali Sajassi (sajassi) <sajassi= > [email protected]> wrote: > > Luc, > > > > Please see my reply inline … > > > > *From: *Luc André Burdet <[email protected]> > *Date: *Monday, June 9, 2025 at 6:57 AM > *To: *Matthew Bocci (Nokia) <[email protected]>, > NVO3 <[email protected]> > *Cc: *[email protected] < > [email protected]>, nvo3-chairs <[email protected]> > *Subject: *Re: WG Last Call for draft-ietf-nvo3-rfc7348bis-00 > > I support this document being published as a standards track document. > > > > To that effect: > > - The status in -00 is still Informational, should it be updated to > Standards Track? > > “Informational” is the correct designation. > > > > - The new Section 8.2 defines “sixteen flag bits” + 16 Reserved, 8 > Reserved. > This is at odds with the field sizes in Section 5 (8 Flags + VNI + 24 > Reserved + 8 Reserved) > > It doesn’t change the reserved bits assignment in the IANA section but > good catch nonetheless for consistency w/ section 5. Will be updated in > the next rev. > > > > Additionally a few nits: > > - The 802 references are rendering as “_02.1X” (underscore?) > - The alignment of bit headers in the figures 1 & 2 is off > >From the XML looks like it was pulled into a bullet-list instead of > the figure itself > > > > Will be taken care of in next rev. > > > > Cheers, > > Ali > > > > Regards, > > Luc André > > > > Luc André Burdet | Cisco | [email protected] | Tel: +1 613 254 > 4814 > > > > > > *From: *Matthew Bocci (Nokia) <[email protected]> > *Date: *Friday, June 6, 2025 at 08:06 > *To: *NVO3 <[email protected]> > *Cc: *[email protected] < > [email protected]>, nvo3-chairs <[email protected]> > *Subject: *[nvo3] WG Last Call for draft-ietf-nvo3-rfc7348bis-00 > > This email begins a working group last call for draft-ietf-nvo3-rfc7348bis-00 > - Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying > Virtualized Layer 2 Networks over Layer 3 Networks > <https://datatracker.ietf.org/doc/draft-ietf-nvo3-rfc7348bis/> > > > > Please review the draft and send any comments to the NVO3 mailing list, > particularly if you do or do not support this draft being published as a > standards track RFC. > > > > An IPR poll was conducted as a part of the very recent adoption poll for > the draft. However, if you have subsequently become aware of any IPR that > was not previously declared, please respond. > > > > There are no IPR disclosures published on the datatracker against either > this draft or RFC7348, and I received no IPR disclosures during WG adoption. > > > > This WG last call closes on Monday 23rd June 2025. > > > > Best regards > > > > Matthew > > _______________________________________________ > nvo3 mailing list -- [email protected] > To unsubscribe send an email to [email protected] > >
_______________________________________________ nvo3 mailing list -- [email protected] To unsubscribe send an email to [email protected]
