Re: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'

[Rabadan, Jorge (Jorge)]

Weiguo,

There are already implementations using value 10 in the RFC5512 BGP encap ext 
community.
That is the value you would have in RFC7432 compliant networks where you can 
also have overlay tunnels. Value 10 would indicate to the ingress PE that the 
route needs an MPLS tunnel to be resolved.

Thx
Jorge

From: BESS > on behalf of 
Haoweiguo >
Date: Tuesday, November 10, 2015 at 1:05 AM
To: "saja...@cisco.com" 
>, 
"jdr...@juniper.net" 
>
Cc: "bess@ietf.org" >
Subject: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'


Hi Ali & John,

The draft of 'draft-ietf-bess-evpn-overlay-02' describes how EVPN can be used 
for Overlay network, the overlay network includes VXLAN, NVGRE and MPLS Over 
GRE.

In section 13 IANA considerations, several overlay tunnel types are requested 
as follows:

8VXLAN Encapsulation
9NVGRE Encapsulation
10   MPLS Encapsulation   (?)
11   MPLS in GRE Encapsulation
12   VXLAN GPE Encapsulation



IMO, 8,9,11 and 12 are all overlay encapsulations, 10 is an exception. Would 
you like to explain what's the purpose of tunnel type 10?



Thanks,

weiguo

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] AD Review of draft-ietf-bess-virtual-subnet-02

[Alvaro Retana (aretana)]

On 11/10/15, 2:18 AM, "Xuxiaohu" 
> wrote:

Xiaohu:

Hi!

We have updated the draft according to your comments and suggestions.

I just have a couple of small items.  Please see my comments below..

I'm going to start the IETF Last Call and put this document up for the IESG 
Telechat on Dec/3.  Please post an update based on the comments below by the 
end of the week.

Thanks!

Alvaro.

. . .
Major:

  1.  The use of rfc2119 keywords is not required.

You left in the rfc2119 boilerplate and reference, please take them off.

...

  1.  You first use "VS" in Section 3.6.  I'm assuming this is related to 
"virtual subnet", but there's no explicit association.

I see that you expanded in 3.6, but now VS is used for the first time in 3.8 
w/out explicitly expanding.

Solution: in 3.6  s/Virtual Subnet/Virtual Subnet (VS)

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] Last Call: (Virtual Subnet: A BGP/MPLS IP VPN-based Subnet Extension Solution) to Informational RFC

[The IESG]

The IESG has received a request from the BGP Enabled Services WG (bess)
to consider the following document:
- 'Virtual Subnet: A BGP/MPLS IP VPN-based Subnet Extension Solution'
   as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
i...@ietf.org mailing lists by 2015-11-24. Exceptionally, comments may be
sent to i...@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes a BGP/MPLS IP VPN-based subnet extension
   solution referred to as Virtual Subnet, which can be used for
   building Layer 3 network virtualization overlays within and/or
   between data centers.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-virtual-subnet/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-bess-virtual-subnet/ballot/


No IPR declarations have been submitted directly on this I-D.


___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] One question about 'draft-ietf-bess-evpn-overlay-02'

[Haoweiguo]

Hi Ali & John,

The draft of 'draft-ietf-bess-evpn-overlay-02' describes how EVPN can be used 
for Overlay network, the overlay network includes VXLAN, NVGRE and MPLS Over 
GRE.

In section 13 IANA considerations, several overlay tunnel types are requested 
as follows:

8VXLAN Encapsulation
9NVGRE Encapsulation
10   MPLS Encapsulation   (?)
11   MPLS in GRE Encapsulation
12   VXLAN GPE Encapsulation



IMO, 8,9,11 and 12 are all overlay encapsulations, 10 is an exception. Would 
you like to explain what's the purpose of tunnel type 10?



Thanks,

weiguo

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] AD Review of draft-ietf-bess-virtual-subnet-02

[Xuxiaohu]

Alvaro,

I will update it ASAP.

Best regards,
Xiaohu

From: Alvaro Retana (aretana) [mailto:aret...@cisco.com]
Sent: Wednesday, November 11, 2015 2:27 AM
To: Xuxiaohu; draft-ietf-bess-virtual-sub...@ietf.org
Cc: VIGOUREUX, MARTIN (MARTIN); bess-cha...@ietf.org; bess@ietf.org
Subject: Re: AD Review of draft-ietf-bess-virtual-subnet-02

On 11/10/15, 2:18 AM, "Xuxiaohu" 
> wrote:

Xiaohu:

Hi!

We have updated the draft according to your comments and suggestions.

I just have a couple of small items.  Please see my comments below..

I'm going to start the IETF Last Call and put this document up for the IESG 
Telechat on Dec/3.  Please post an update based on the comments below by the 
end of the week.

Thanks!

Alvaro.

. . .
Major:

  1.  The use of rfc2119 keywords is not required.

You left in the rfc2119 boilerplate and reference, please take them off.

...

  1.  You first use "VS" in Section 3.6.  I'm assuming this is related to 
"virtual subnet", but there's no explicit association.

I see that you expanded in 3.6, but now VS is used for the first time in 3.8 
w/out explicitly expanding.

Solution: in 3.6  s/Virtual Subnet/Virtual Subnet (VS)

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

[bess] I-D Action: draft-ietf-bess-virtual-subnet-04.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the BGP Enabled Services Working Group of the 
IETF.

Title   : Virtual Subnet: A BGP/MPLS IP VPN-based Subnet 
Extension Solution
Authors : Xiaohu Xu
  Robert Raszuk
  Christian Jacquenet
  Truman Boyes
  Brendan Fee
Filename: draft-ietf-bess-virtual-subnet-04.txt
Pages   : 14
Date: 2015-11-10

Abstract:
   This document describes a BGP/MPLS IP VPN-based subnet extension
   solution referred to as Virtual Subnet, which can be used for
   building Layer 3 network virtualization overlays within and/or
   between data centers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bess-virtual-subnet/

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-virtual-subnet-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/

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'

[Haoweiguo]

Jorge,

Thanks for your explanations. However, i still can't understand, i'm sorry.

RFC 5512 only defines IP tunnel type and encapsulation attribute, like 
L2TPv3,GRE and IP in IP.  For RFC 5512, MPLS tunnel doesn't need to be defined 
specifically, it is default case. In RFC 7432, the tunnel type 10 also hasn't 
been defined. Later, when the EVPN for overlay network solution was proposed, 
the tunnel type 10 was introduced to differentiate MPLS tunnel and 
VXLAN/NVGRE/MPLS Over GRE tunnel, because same route type 1,2,3,4 and 5 are 
used in both RFC 7432 and the draft 'draft-ietf-bess-evpn-overlay-02'. We need 
the tunnel type to clearly notify peer EVPN PE which tunnel(including MPLS 
tunnel type) should be used.  So it introduced updates on RFC 7432 and will 
incur some interoperbility issue for RFC 7432. Am i right?

Thanks,

weiguo





From: BESS [bess-boun...@ietf.org] on behalf of Rabadan, Jorge (Jorge) 
[jorge.raba...@alcatel-lucent.com]
Sent: Wednesday, November 11, 2015 0:01
To: Haoweiguo; saja...@cisco.com; jdr...@juniper.net
Cc: bess@ietf.org
Subject: Re: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'

Weiguo,

There are already implementations using value 10 in the RFC5512 BGP encap ext 
community.
That is the value you would have in RFC7432 compliant networks where you can 
also have overlay tunnels. Value 10 would indicate to the ingress PE that the 
route needs an MPLS tunnel to be resolved.

Thx
Jorge

From: BESS > on behalf of 
Haoweiguo >
Date: Tuesday, November 10, 2015 at 1:05 AM
To: "saja...@cisco.com" 
>, 
"jdr...@juniper.net" 
>
Cc: "bess@ietf.org" >
Subject: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'


Hi Ali & John,

The draft of 'draft-ietf-bess-evpn-overlay-02' describes how EVPN can be used 
for Overlay network, the overlay network includes VXLAN, NVGRE and MPLS Over 
GRE.

In section 13 IANA considerations, several overlay tunnel types are requested 
as follows:

8VXLAN Encapsulation
9NVGRE Encapsulation
10   MPLS Encapsulation   (?)
11   MPLS in GRE Encapsulation
12   VXLAN GPE Encapsulation



IMO, 8,9,11 and 12 are all overlay encapsulations, 10 is an exception. Would 
you like to explain what's the purpose of tunnel type 10?



Thanks,

weiguo

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'

[Rabadan, Jorge (Jorge)]

Weiguo,

Well, if an RFC7432 implementation does not use the RFC5512 ext community, the 
following sentence in the evan-overlay draft should help interoperability. I 
personally don’t see any issues.


If the BGP Encapsulation extended community is not present, then the
   default MPLS encapsulation or a statically configured encapsulation
   is assumed.

Thanks.
Jorge

From: Haoweiguo >
Date: Tuesday, November 10, 2015 at 7:03 PM
To: Jorge Rabadan 
>, 
"saja...@cisco.com" 
>, 
"jdr...@juniper.net" 
>
Cc: "bess@ietf.org" >
Subject: RE: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'


Jorge,

Thanks for your explanations. However, i still can't understand, i'm sorry.

RFC 5512 only defines IP tunnel type and encapsulation attribute, like 
L2TPv3,GRE and IP in IP.  For RFC 5512, MPLS tunnel doesn't need to be defined 
specifically, it is default case. In RFC 7432, the tunnel type 10 also hasn't 
been defined. Later, when the EVPN for overlay network solution was proposed, 
the tunnel type 10 was introduced to differentiate MPLS tunnel and 
VXLAN/NVGRE/MPLS Over GRE tunnel, because same route type 1,2,3,4 and 5 are 
used in both RFC 7432 and the draft 'draft-ietf-bess-evpn-overlay-02'. We need 
the tunnel type to clearly notify peer EVPN PE which tunnel(including MPLS 
tunnel type) should be used.  So it introduced updates on RFC 7432 and will 
incur some interoperbility issue for RFC 7432. Am i right?

Thanks,

weiguo





From: BESS [bess-boun...@ietf.org] on behalf of 
Rabadan, Jorge (Jorge) 
[jorge.raba...@alcatel-lucent.com]
Sent: Wednesday, November 11, 2015 0:01
To: Haoweiguo; saja...@cisco.com; 
jdr...@juniper.net
Cc: bess@ietf.org
Subject: Re: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'

Weiguo,

There are already implementations using value 10 in the RFC5512 BGP encap ext 
community.
That is the value you would have in RFC7432 compliant networks where you can 
also have overlay tunnels. Value 10 would indicate to the ingress PE that the 
route needs an MPLS tunnel to be resolved.

Thx
Jorge

From: BESS > on behalf of 
Haoweiguo >
Date: Tuesday, November 10, 2015 at 1:05 AM
To: "saja...@cisco.com" 
>, 
"jdr...@juniper.net" 
>
Cc: "bess@ietf.org" >
Subject: [bess] One question about 'draft-ietf-bess-evpn-overlay-02'


Hi Ali & John,

The draft of 'draft-ietf-bess-evpn-overlay-02' describes how EVPN can be used 
for Overlay network, the overlay network includes VXLAN, NVGRE and MPLS Over 
GRE.

In section 13 IANA considerations, several overlay tunnel types are requested 
as follows:

8VXLAN Encapsulation
9NVGRE Encapsulation
10   MPLS Encapsulation   (?)
11   MPLS in GRE Encapsulation
12   VXLAN GPE Encapsulation



IMO, 8,9,11 and 12 are all overlay encapsulations, 10 is an exception. Would 
you like to explain what's the purpose of tunnel type 10?



Thanks,

weiguo

___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess