Re: [nvo3] I-D Action: draft-ietf-nvo3-geneve-04.txt

This document shows IPv6 encapsulation, but provides no guidance about setting the Outer IPv6 flow label.
I would expect the flow label to be described with similar language to the UDP source port, since Flow Label is the obvious way to load-balance traffic across links.

Also, I don't know why the Outer Ethernet header is specified in the packet format. I think the Outer IPv4 could be carried in any link-layer or pseudo-wire. Or is the intent that this encapsulation is only valid on physical Ethernet?

-Dave

-----Original Message-----
From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Ganga, Ilango S
Sent: Tuesday, March 14, 2017 6:56 AM
To: nvo3@ietf.org
Subject: Re: [nvo3] I-D Action: draft-ietf-nvo3-geneve-04.txt

Hi All,

As per the direction from the NVO3 virtual interim meeting on Mar 01, 2017, we have updated the Geneve draft to reflect the recommendations from the NVO3 Encap Design Team.

Regards,
Ilango

-----Original Message-----
From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Monday, March 13, 2017 2:56 PM
To: i-d-announce@ietf.org
Cc: nvo3@ietf.org
Subject: [nvo3] I-D Action: draft-ietf-nvo3-geneve-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Network Virtualization Overlays of the IETF.

        Title           : Geneve: Generic Network Virtualization Encapsulation
        Authors         : Jesse Gross
                          Ilango Ganga
                          T. Sridhar
	Filename        : draft-ietf-nvo3-geneve-04.txt
	Pages           : 26
	Date            : 2017-03-13

Abstract:
   Network virtualization involves the cooperation of devices with a
   wide variety of capabilities such as software and hardware tunnel
   endpoints, transit fabrics, and centralized control clusters.  As a
   result of their role in tying together different elements in the
   system, the requirements on tunnels are influenced by all of these
   components.  Flexibility is therefore the most important aspect of a
   tunnel protocol if it is to keep pace with the evolution of the
   system.  This draft describes Geneve, a protocol designed to
   recognize and accommodate these changing capabilities and needs.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-nvo3-geneve/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-nvo3-geneve-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-nvo3-geneve-04

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3

_______________________________________________
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3