Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang

["Susan Hares" <[e-mail]>]

Support for draft-shah-bess-l2vpn-yang.  It is a good start to this model. 

+1 to Giles comment that the bgp-parameters structure needs to be harmonized draft-dhjain-bess-bgp-l3vpn-yang. 

Both draft-shah-bess-l2vpn-yang and draft-dhjain-bess-bgp-l3vpn-yang should reference the base bgp model (draft-idr-bgp-model) as the bgp parameters should link to a bgp peer.   

How is this linkage occurring in the models? Are you simply augmenting the base BGP specification?  Is it true that your bgp-parameters do not require any policy? 

Sue Hares 

-----Original Message-----
From: BESS [mailto:[e-mail]] On Behalf Of Shah, Himanshu
Sent: Wednesday, May 11, 2016 4:34 PM
To: Giles Heron; Thomas Morin; Carl Moberg (camoberg)
Cc: [e-mail]; [e-mail]
Subject: Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang

Hi Giles -

Thanks for your support.
We will work through your comments as highest priority through the next iteration of the draft.

Thanks,
Himanshu

-----Original Message-----
From: BESS [mailto:[e-mail]] On Behalf Of Giles Heron
Sent: Friday, May 06, 2016 4:13 PM
To: Thomas Morin; Carl Moberg (camoberg)
Cc: [e-mail]; [e-mail]
Subject: Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang

Hi Thomas,

I support this document being adopted.

However I would like to see the comments that Carl Moberg and I brought to the authors in Prague get addressed (they still seem to be outstanding).   Sorry - I should have followed up on those before now.

There’s also some degree of overlap with draft-brissette-bess-evpn-yang, and with draft-dhjain-bess-bgp-l3vpn-yang-01, and I’d like to see common components (e.g. BGP RTs/RDs) being abstracted into common models.

Giles

> On 4 May 2016, at 15:17, Thomas Morin <[e-mail]> wrote:
> 
> Hello working group,
> 
> This email starts a two-week poll on adopting 
> draft-shah-bess-l2vpn-yang [1] as a working group document.
> 
> Please state on the list if you support adoption or not (in both cases, please also state the reasons).
> 
> This poll runs until *May 25th*.
> 
> This call runs in parallel with the adoption call on draft-brissette-bess-evpn-yang hence the extended period.
> 
> 
> We are *coincidentally* also polling for knowledge of any other IPR 
> that applies to this draft, 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 please 
> respond to this email and indicate whether or not you are aware of any 
> relevant IPR.
> 
> The draft will not be adopted until a response has been received from 
> each author and contributor.
> 
> If you are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.
> 
> Thank you,
> 
> Martin & Thomas
> bess chairs
> 
> [1] https://datatracker.ietf.org/doc/draft-shah-bess-l2vpn-yang
> 
> _______________________________________________
> BESS mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bess

_______________________________________________
BESS mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/bess
_______________________________________________
BESS mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/bess