I support the WG adoption of this draft.

Regards,
-Dhananjaya



>

> On Apr 28, 2025 at 3:23 AM, Matthew Bocci (Nokia)  
> <[email protected]><mailto:&lt;[email protected]&gt;>  wrote:

>

>

>

>

>  This email begins a two-week poll for   adoption   for   
> draft-md-nvo3-rfc7348bis-00 - Virtual eXtensible Local Area Network (VXLAN): 
> A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks 
>    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.

>

>

>

>

>

>

>

>  Note that supporting working group   adoption   indicates that you think the 
> draft is headed in the right direction and represents a piece of work that 
> the working group should take on and progress. It does not have to be 
> technically perfect at this stage.

>

>

>

>

>

>

>

>  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, copying the NVo3 mailing list.

>

>

>

>

>

>

>

>  Currently, there are no IPR disclosures in the datatracker against this 
> document or the original RFC7348.

>

>

>

>

>

>

>

>  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 closes on Monday 12th May 2025.

>

>

>

>

>

>

>

>  Regards

>

>

>

>  Matthew and Sam

>

>

>

>

>

>

>



_______________________________________________
nvo3 mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to