date:20170214

Re: [bess] BGP common parameter Yang module

2017-02-14 Thread Acee Lindem (acee)

Hi Dhanendra,

From: "Dhanendra Jain (dhjain)" >
Date: Tuesday, February 14, 2017 at 4:12 PM
To: Acee Lindem >, Xufeng Liu 
>, "Patrice 
Brissette (pbrisset)" >, Jeff 
Tantsura >, 'Giles 
Heron' >
Cc: 
"draft-ietf-rtgwg-routing-ty...@ietf.org"
 
>,
 "bess@ietf.org" >, 
Himanshu Shah >
Subject: Re: [bess] BGP common parameter Yang module

Hi Acee,

From: "Acee Lindem (acee)" >
Date: Tuesday, February 14, 2017 at 12:51 PM
To: Cisco Employee >, Xufeng Liu 
>, "Patrice 
Brissette (pbrisset)" >, 'Jeff 
Tantsura' >, 'Giles 
Heron' >
Cc: 
"draft-ietf-rtgwg-routing-ty...@ietf.org"
 
>,
 "bess@ietf.org" >, 
"'Shah, Himanshu'" >
Subject: Re: [bess] BGP common parameter Yang module

See inline.

From: "Dhanendra Jain (dhjain)" >
Date: Tuesday, February 14, 2017 at 3:45 PM
To: Xufeng Liu >, 
Acee Lindem >, "Patrice Brissette 
(pbrisset)" >, Jeff Tantsura 
>, 'Giles Heron' 
>
Cc: 
"draft-ietf-rtgwg-routing-ty...@ietf.org"
 
>,
 "bess@ietf.org" >, 
Himanshu Shah >
Subject: Re: [bess] BGP common parameter Yang module

Hi Xefeng,

From: Xufeng Liu >
Date: Tuesday, February 14, 2017 at 11:44 AM
To: Cisco Employee >, "Acee Lindem 
(acee)" >, "Patrice Brissette (pbrisset)" 
>, 'Jeff Tantsura' 
>, 'Giles Heron' 
>
Cc: 
"draft-ietf-rtgwg-routing-ty...@ietf.org"
 
>,
 "bess@ietf.org" >, 
"'Shah, Himanshu'" >
Subject: RE: [bess] BGP common parameter Yang module

Hi Dhanendra,

More below.
Thanks,

- Xufeng

From: Dhanendra Jain (dhjain) [mailto:dhj...@cisco.com]
Sent: Tuesday, February 14, 2017 2:27 PM
To: Xufeng Liu >; 
Acee Lindem (acee) >; Patrice Brissette 
(pbrisset) >; 'Jeff Tantsura' 
>; 'Giles Heron' 
>
Cc: 
draft-ietf-rtgwg-routing-ty...@ietf.org;
 bess@ietf.org; 'Shah, Himanshu' 
>
Subject: Re: [bess] BGP common parameter Yang module

Hi Xufeng,

inline..

From: Xufeng Liu >
Date: Monday, February 13, 2017 at 7:21 AM
To: "Acee Lindem (acee)" >, "Patrice 
Brissette (pbrisset)" >, 'Jeff 
Tantsura' >, 'Giles 
Heron' >
Cc: 
"draft-ietf-rtgwg-routing-ty...@ietf.org"
 
>,
 Cisco Employee >, 
"bess@ietf.org" >, 
"'Shah,

Re: [bess] BGP common parameter Yang module

2017-02-14 Thread Dhanendra Jain (dhjain)

Hi Xufeng,

inline..

From: Xufeng Liu >
Date: Monday, February 13, 2017 at 7:21 AM
To: "Acee Lindem (acee)" >, "Patrice 
Brissette (pbrisset)" >, 'Jeff 
Tantsura' >, 'Giles 
Heron' >
Cc: 
"draft-ietf-rtgwg-routing-ty...@ietf.org"
 
>,
 Cisco Employee >, 
"bess@ietf.org" >, 
"'Shah, Himanshu'" >
Subject: RE: [bess] BGP common parameter Yang module

In EVPN, as Patrice described, the structure is:

  | +--rw bgp-parameters
  | |  +--rw common
  | | +--rw rd-rt* [route-distinguisher]
  | |+--rw route-distinguisherstring
  | |+--rw vpn-target* [rt-value]
  | |   +--rw rt-valuestring
  | |   +--rw rt-type bgp-rt-type

In L2VPN, the structure is:
 +--ro bgp-auto-discovery
 |  +--ro route-distinguisher?   string
 |  +--ro vpn-target* [rt-value]
 |  |  +--ro rt-valuestring
 |  |  +--ro rt-type bgp-rt-type

In L3VPN, the current structure is:
  +--rw route-distinguisher
  |  +--rw config
  |  |  +--rw rd?   string
  +--rw ipv4
  |  +--rw unicast
  | +--rw route-targets
  | |  +--rw config
  | |  |  +--rw rts* [rt]
  | |  |  |  +--rw rt string
  | |  |  |  +--rw rt-type?   Enumeration
  +--rw ipv6
 +--rw unicast
+--rw route-targets
|  +--rw config
|  |  +--rw rts* [rt]
|  |  |  +--rw rt string
|  |  |  +--rw rt-type?   enumeration

Hi Dhanendra and All,

Are we ok to move the route targets section out of the AF specific location to 
where RD is specified? If so, we can define the following common grouping:

Dhjain> I think one way to handle this is to have separate common groupings for 
RD and RT. So that we can retain AF level granularity for RT grouping for 
import/export rules.

Thanks,
Dhanendra.

 |  +--ro route-distinguisher?   string
 |  +--ro vpn-target* [rt-value]
 |  |  +--ro rt-valuestring
 |  |  +--ro rt-type bgp-rt-type

Otherwise, we can only define a grouping without the RD:

 |  +--ro vpn-target* [rt-value]
 |  |  +--ro rt-valuestring
 |  |  +--ro rt-type bgp-rt-type
Thanks,
- Xufeng


From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Saturday, February 11, 2017 12:46 PM
To: Patrice Brissette (pbrisset) 
>; Jeff Tantsura 
>; Giles Heron 
>
Cc: 
draft-ietf-rtgwg-routing-ty...@ietf.org;
 Dhanendra Jain (dhjain) >; 
bess@ietf.org; Shah, Himanshu 
>
Subject: Re: [bess] BGP common parameter Yang module

Given that there is no paucity of authors and contributors on these three BESS 
YANG models, I’d hope that one of them could provide a suggested common 
grouping. For now, I’ve added the route-target-type type on which there seems 
to be consensus.

Thanks,
Acee

From: "Patrice Brissette (pbrisset)" 
>
Date: Saturday, February 11, 2017 at 8:23 AM
To: Jeff Tantsura >, 
Acee Lindem >, Giles Heron 
>
Cc: Himanshu Shah >, 
"bess@ietf.org" >, 
"Dhanendra Jain (dhjain)" >
Subject: Re: [bess] BGP common parameter Yang module

Hi Folks,

Same here. Can we do something about it?  And agree, all 3 VPN models should 
have the same commonality.

Regards,
Patrice Brissette

From: Jeff Tantsura >
Date: Friday, February 10, 2017 at 2:43 PM
To: "Acee Lindem (acee)" >, Giles Heron 
>
Cc: Patrice Brissette >, "Shah, 
Himanshu" >, 
"bess@ietf.org" >,

Re: [bess] WG Last Call for draft-ietf-bess-evpn-prefix-advertisement-04

2017-02-14 Thread John E Drake

Support and I'm not aware of any IPR

Yours Irrespectively,

John


> -Original Message-
> From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Martin Vigoureux
> Sent: Monday, February 13, 2017 5:08 PM
> To: BESS 
> Subject: [bess] WG Last Call for draft-ietf-bess-evpn-prefix-advertisement-04
> 
> Hello Working Group,
> 
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-prefix-advertisement-04 [1] which is considered mature 
> and
> ready for a final working group review.
> Note that this call is longer than usual because we are pushing two correlated
> documents together.
> 
> Please read this document if you haven't read the most recent version yet, and
> send your comments to the list, no later than *5th of March*.
> Note that this is *not only* a call for comments on the document; it is also 
> a call
> for support (or not) to publish this document as a Proposed Standard RFC.
> 
> *Coincidentally*, we are also polling for knowledge of any IPR that applies to
> draft-ietf-bess-evpn-prefix-advertisement, 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 a document author or contributor of
> draft-ietf-bess-evpn-prefix-advertisement-04 please respond to this email and
> indicate whether or not you are aware of any relevant IPR.
> 
> Note that, as of today, no IPR has been disclosed against this document or its
> earlier versions.
> 
> We are also polling for knowledge of implementations of part or all of what 
> this
> document specifies. This information is expected as per [2].
> Please inform the mailing list, or the chairs, or only one of the chairs.
> 
> Thank you,
> M
> 
> [1]
> https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-prefix-advertisement/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> 
> ___
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess

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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

2017-02-14 Thread Ali Sajassi (sajassi)


Support as co-auhtor. Not aware of any non-disclosed IPR.

Regards,
Ali



On 2/13/17, 2:07 PM, "BESS on behalf of Martin Vigoureux"
 wrote:

>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered
>mature and ready for a final working group review.
>Note that this call is longer than usual because we are pushing two
>correlated documents together.
>
>Please read this document if you haven't read the most recent
>version yet, and send your comments to the list, no later than
>*5th of March*.
>Note that this is *not only* a call for comments on the document; it is
>also a call for support (or not) to publish this document as a Proposed
>Standard RFC.
>
>*Coincidentally*, we are also polling for knowledge of any IPR that
>applies to draft-ietf-bess-evpn-inter-subnet-forwarding, 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 a document author or contributor of
>draft-ietf-bess-evpn-inter-subnet-forwarding-03 please respond to this
>email and indicate whether or not you are aware of any relevant IPR.
>
>Note that, as of today, no IPR has been disclosed against this document
>or its earlier versions.
>
>We are also polling for knowledge of implementations of part or all of
>what this document specifies. This information is expected as per [2].
>Please inform the mailing list, or the chairs, or only one of the chairs.
>
>Thank you,
>M
>
>[1] 
>https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-inter-subnet-forward
>ing/
>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>___
>BESS mailing list
>BESS@ietf.org
>https://www.ietf.org/mailman/listinfo/bess

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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-prefix-advertisement-04

2017-02-14 Thread Ali Sajassi (sajassi)


Support as co-auhtor. Not aware of any non-disclosed IPR.

Regards,
Ali

On 2/13/17, 2:07 PM, "BESS on behalf of Martin Vigoureux"
 wrote:

>Hello Working Group,
>
>This email starts a Working Group Last Call on
>draft-ietf-bess-evpn-prefix-advertisement-04 [1] which is considered
>mature and ready for a final working group review.
>Note that this call is longer than usual because we are pushing two
>correlated documents together.
>
>Please read this document if you haven't read the most recent
>version yet, and send your comments to the list, no later than
>*5th of March*.
>Note that this is *not only* a call for comments on the document; it is
>also a call for support (or not) to publish this document as a Proposed
>Standard RFC.
>
>*Coincidentally*, we are also polling for knowledge of any IPR that
>applies to draft-ietf-bess-evpn-prefix-advertisement, 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 a document author or contributor of
>draft-ietf-bess-evpn-prefix-advertisement-04 please respond to this
>email and indicate whether or not you are aware of any relevant IPR.
>
>Note that, as of today, no IPR has been disclosed against this document
>or its earlier versions.
>
>We are also polling for knowledge of implementations of part or all of
>what this document specifies. This information is expected as per [2].
>Please inform the mailing list, or the chairs, or only one of the chairs.
>
>Thank you,
>M
>
>[1] 
>https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-prefix-advertisement
>/
>[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
>___
>BESS mailing list
>BESS@ietf.org
>https://www.ietf.org/mailman/listinfo/bess

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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

2017-02-14 Thread Liu, Hua


Yes/Support

Regards,
Autumn

On 2/13/17, 11:07 PM, "BESS on behalf of Martin Vigoureux" 
 wrote:

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is 
considered 
mature and ready for a final working group review.
Note that this call is longer than usual because we are pushing two 
correlated documents together.

Please read this document if you haven't read the most recent
version yet, and send your comments to the list, no later than
*5th of March*.
Note that this is *not only* a call for comments on the document; 
it is 
also a call for support (or not) to publish this document as a 
Proposed 
Standard RFC.

*Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-evpn-inter-subnet-forwarding, 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 a document author or contributor of
draft-ietf-bess-evpn-inter-subnet-forwarding-03 please respond to 
this 
email and indicate whether or not you are aware of any relevant IPR.

Note that, as of today, no IPR has been disclosed against this 
document 
or its earlier versions.

We are also polling for knowledge of implementations of part or all 
of 
what this document specifies. This information is expected as per 
[2]. 
Please inform the mailing list, or the chairs, or only one of the 
chairs.

Thank you,
M

[1] 

https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-inter-subnet-forwarding/
[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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


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


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


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

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

2017-02-14 Thread Jeff Tantsura

yes/support
 
Cheers,
Jeff
 
On 2/13/17, 11:07 PM, "BESS on behalf of Martin Vigoureux" 
 wrote:

Hello Working Group,

This email starts a Working Group Last Call on 
draft-ietf-bess-evpn-inter-subnet-forwarding-03 [1] which is considered 
mature and ready for a final working group review.
Note that this call is longer than usual because we are pushing two 
correlated documents together.

Please read this document if you haven't read the most recent
version yet, and send your comments to the list, no later than
*5th of March*.
Note that this is *not only* a call for comments on the document; it is 
also a call for support (or not) to publish this document as a Proposed 
Standard RFC.

*Coincidentally*, we are also polling for knowledge of any IPR that 
applies to draft-ietf-bess-evpn-inter-subnet-forwarding, 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 a document author or contributor of
draft-ietf-bess-evpn-inter-subnet-forwarding-03 please respond to this 
email and indicate whether or not you are aware of any relevant IPR.

Note that, as of today, no IPR has been disclosed against this document 
or its earlier versions.

We are also polling for knowledge of implementations of part or all of 
what this document specifies. This information is expected as per [2]. 
Please inform the mailing list, or the chairs, or only one of the 
chairs.

Thank you,
M

[1] 

https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-inter-subnet-forwarding/
[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

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



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

Re: [bess] BGP common parameter Yang module

Re: [bess] BGP common parameter Yang module

Re: [bess] WG Last Call for draft-ietf-bess-evpn-prefix-advertisement-04

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

Re: [bess] WG Last Call for draft-ietf-bess-evpn-prefix-advertisement-04

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

Re: [bess] WG Last Call for draft-ietf-bess-evpn-inter-subnet-forwarding-03

7 matches

Site Navigation

Mail list logo

Footer information