Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang
Yes/support On 5/4/16, 7:17 AM, "BESS on behalf of Thomas Morin"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 >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] Poll for adoption: draft-shah-bess-l2vpn-yang
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:bess-boun...@ietf.org] On Behalf Of Shah, Himanshu Sent: Wednesday, May 11, 2016 4:34 PM To: Giles Heron; Thomas Morin; Carl Moberg (camoberg) Cc: bess@ietf.org; draft-shah-bess-l2vpn-y...@tools.ietf.org 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:bess-boun...@ietf.org] On Behalf Of Giles Heron Sent: Friday, May 06, 2016 4:13 PM To: Thomas Morin; Carl Moberg (camoberg) Cc: bess@ietf.org; draft-shah-bess-l2vpn-y...@tools.ietf.org 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 <thomas.mo...@orange.com> 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 > 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] Poll for adoption: draft-shah-bess-l2vpn-yang
Resending due to mail delivery messages Support as co-author Not aware of any relevant IPR Thanks, Tapraj On 5/5/16, 9:43 AM, "Tapraj Singh (tapsingh)" <tapsi...@cisco.com> wrote: >As a co-author, I support this draft. > > >Thanks >Tapraj > >On 5/5/16, 7:48 AM, "BESS on behalf of Shah, Himanshu" ><bess-boun...@ietf.org on behalf of hs...@ciena.com> wrote: > >>Support as co-author. >>I am not aware of any IPR that applies to this draft. >> >>Himanshu using iPad (so excuse the auto-corrects...) >> >>From: BESS [bess-boun...@ietf.org] On Behalf Of Luay Jalil >>[luayja...@gmail.com] >>Sent: Thursday, May 05, 2016 6:23 AM >>To: Thomas Morin >>Cc: BESS; draft-shah-bess-l2vpn-y...@tools.ietf.org >>Subject: Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang >> >>Resending due to mail delivery messages >> >>Support as co-author >> >>Not aware of any relevant IPR >> >>Thanks, >>Luay >> >>On May 4, 2016 9:18 AM, "Thomas Morin" >><thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>> 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 >>BESS@ietf.org<mailto: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] Poll for adoption: draft-shah-bess-l2vpn-yang
Thanks Himanshu, That all sounds reasonable. Adrian > -Original Message- > From: Shah, Himanshu [mailto:hs...@ciena.com] > Sent: 25 May 2016 14:16 > To: adr...@olddog.co.uk; 'Thomas Morin'; bess@ietf.org > Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org > Subject: RE: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > > Hi Adrian - > > Appreciate your detail review and the comments. > Please see below inline responses to your comments.. > > Thanks, > Himanshu > > > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Adrian Farrel > Sent: Tuesday, May 24, 2016 8:52 AM > To: 'Thomas Morin'; bess@ietf.org > Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org > Subject: Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > > Hi Thomas, > > I'm not opposed to this work at all. But I think that the extensive use of the word > "service" in the document may cause a load of confusion. > > As far as I can see, this YANG model is about operating and monitoring the > network components and protocols that are used to realize (deliver) the service. > This is all information that the network operator (service provider) cares about > deeply, and that the equipment vendor must understand. But a lot of it is beyond > the concern (or understanding) of the service consumer who has requested the > service. > > If I might compare with the work of L3SM, we need to distinguish between the > "service model" on the interface between the customer and the operator, and > the "service delivery model" on the northbound interface of an orchestrator". It > may be helpful to consider two separate conceptual components: a "service > orchestrator" that consumes a service model, and a "network orchestrator" that > consumes the model in this document and uses it to work out what to tell > protocols, network controller, etc. > > Perhaps the document could be enhanced by a little extra text explaining how > the model will be used. This need not be pages and pages, just a simple > statement that, for example, it is expected that this model will be used by the > management tools run by network operators in order to manage and monitor the > network resources that they use to deliver L2VPN services. > > [Himanshu>] Agreed. Will clarify the purpose of the draft as you suggest above. > > > Might I ask also that one sentence is removed from the Abstract *before* > adoption? >This is a >living document and contains aspects of object models that have been >discussed extensively in the working group with consensus. > It is not the place of the authors to claim consensus for the content of the > document: that call belongs to the WG chairs in response to targeted questions > to the WG. WG adoption is not a measure by which to determine consensus for > the content of the document, either. > > Additionally, the Introduction has: >The definition work is undertaken initially by a smaller >working group with members representing various vendors and service >providers. > I'm sure you don't mean to imply any subversion of the IETF process, and I am > equally sure that this is just a matter of English usage. > I think you need... >The definition work was initially undertaken initially by a small >group of co-authors with members representing various vendors and service >providers. > > [Himanshu>] Agreed on this as well. Did not mean to shortcut the due process at > IETF > [Himanshu>] > > Again, this change needs to be made before adoption. > > [Himanshu>] > [Himanshu>] Will update the draft to address your comments in the -00- version > of the WG draft. > Does that work for you? > > > Thanks, > Adrian > > > -Original Message- > > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin > > Sent: 04 May 2016 15:18 > > To: bess@ietf.org > > Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org > > Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > > > > 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,
Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang
Hi Adrian - Appreciate your detail review and the comments. Please see below inline responses to your comments.. Thanks, Himanshu -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Adrian Farrel Sent: Tuesday, May 24, 2016 8:52 AM To: 'Thomas Morin'; bess@ietf.org Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org Subject: Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang Hi Thomas, I'm not opposed to this work at all. But I think that the extensive use of the word "service" in the document may cause a load of confusion. As far as I can see, this YANG model is about operating and monitoring the network components and protocols that are used to realize (deliver) the service. This is all information that the network operator (service provider) cares about deeply, and that the equipment vendor must understand. But a lot of it is beyond the concern (or understanding) of the service consumer who has requested the service. If I might compare with the work of L3SM, we need to distinguish between the "service model" on the interface between the customer and the operator, and the "service delivery model" on the northbound interface of an orchestrator". It may be helpful to consider two separate conceptual components: a "service orchestrator" that consumes a service model, and a "network orchestrator" that consumes the model in this document and uses it to work out what to tell protocols, network controller, etc. Perhaps the document could be enhanced by a little extra text explaining how the model will be used. This need not be pages and pages, just a simple statement that, for example, it is expected that this model will be used by the management tools run by network operators in order to manage and monitor the network resources that they use to deliver L2VPN services. [Himanshu>] Agreed. Will clarify the purpose of the draft as you suggest above. Might I ask also that one sentence is removed from the Abstract *before* adoption? This is a living document and contains aspects of object models that have been discussed extensively in the working group with consensus. It is not the place of the authors to claim consensus for the content of the document: that call belongs to the WG chairs in response to targeted questions to the WG. WG adoption is not a measure by which to determine consensus for the content of the document, either. Additionally, the Introduction has: The definition work is undertaken initially by a smaller working group with members representing various vendors and service providers. I'm sure you don't mean to imply any subversion of the IETF process, and I am equally sure that this is just a matter of English usage. I think you need... The definition work was initially undertaken initially by a small group of co-authors with members representing various vendors and service providers. [Himanshu>] Agreed on this as well. Did not mean to shortcut the due process at IETF [Himanshu>] Again, this change needs to be made before adoption. [Himanshu>] [Himanshu>] Will update the draft to address your comments in the -00- version of the WG draft. Does that work for you? Thanks, Adrian > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin > Sent: 04 May 2016 15:18 > To: bess@ietf.org > Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org > Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > > 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 > >
Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang
Yes/support -Original Message- >>From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin >>Sent: Wednesday, May 04, 2016 10:18 AM >>To: bess@ietf.org >>Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org >>Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang >> >>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 >>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] Poll for adoption: draft-shah-bess-l2vpn-yang
Hi WG/chairs, As a co-author, I support the adoption of this draft. I am also not aware of any IPR associated with this draft. Regards. ‹ Kamran Raza On 2016-05-23, 1:31 PM, "Shah, Himanshu" <hs...@ciena.com> wrote: >Including kamran raza.. > >Thanks, >Himanshu > > >-Original Message- >From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin >Sent: Wednesday, May 04, 2016 10:18 AM >To: bess@ietf.org >Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org >Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > >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 >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] Poll for adoption: draft-shah-bess-l2vpn-yang
Hi Thomas, I'm not opposed to this work at all. But I think that the extensive use of the word "service" in the document may cause a load of confusion. As far as I can see, this YANG model is about operating and monitoring the network components and protocols that are used to realize (deliver) the service. This is all information that the network operator (service provider) cares about deeply, and that the equipment vendor must understand. But a lot of it is beyond the concern (or understanding) of the service consumer who has requested the service. If I might compare with the work of L3SM, we need to distinguish between the "service model" on the interface between the customer and the operator, and the "service delivery model" on the northbound interface of an orchestrator". It may be helpful to consider two separate conceptual components: a "service orchestrator" that consumes a service model, and a "network orchestrator" that consumes the model in this document and uses it to work out what to tell protocols, network controller, etc. Perhaps the document could be enhanced by a little extra text explaining how the model will be used. This need not be pages and pages, just a simple statement that, for example, it is expected that this model will be used by the management tools run by network operators in order to manage and monitor the network resources that they use to deliver L2VPN services. Might I ask also that one sentence is removed from the Abstract *before* adoption? This is a living document and contains aspects of object models that have been discussed extensively in the working group with consensus. It is not the place of the authors to claim consensus for the content of the document: that call belongs to the WG chairs in response to targeted questions to the WG. WG adoption is not a measure by which to determine consensus for the content of the document, either. Additionally, the Introduction has: The definition work is undertaken initially by a smaller working group with members representing various vendors and service providers. I'm sure you don't mean to imply any subversion of the IETF process, and I am equally sure that this is just a matter of English usage. I think you need... The definition work was initially undertaken initially by a small group of co-authors with members representing various vendors and service providers. Again, this change needs to be made before adoption. Thanks, Adrian > -Original Message- > From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin > Sent: 04 May 2016 15:18 > To: bess@ietf.org > Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org > Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > > 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 > 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] Poll for adoption: draft-shah-bess-l2vpn-yang
I support this draft as a co-author and I am not aware of any relevant IPR. Regards, Patrice Patrice Brissette TECHNICAL LEADER.ENGINEERING pbris...@cisco.com Phone: +1 613 254 3336 Cisco Systems Canada Co. / Les Systemes Cisco Canada CIE Canada Cisco.com <http://www.cisco.com/global/CA/> On 2016-05-23, 1:31 PM, "Shah, Himanshu" <hs...@ciena.com> wrote: >Including kamran raza.. > >Thanks, >Himanshu > > >-Original Message- >From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin >Sent: Wednesday, May 04, 2016 10:18 AM >To: bess@ietf.org >Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org >Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > >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 >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] Poll for adoption: draft-shah-bess-l2vpn-yang
Including kamran raza.. Thanks, Himanshu -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin Sent: Wednesday, May 04, 2016 10:18 AM To: bess@ietf.org Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang 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 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] Poll for adoption: draft-shah-bess-l2vpn-yang
I am not aware of any IPR related to the draft. Regards Matthew On 04/05/2016, 15:17, "thomas.mo...@orange.com"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 BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang
I support adoption of this draft as a co-author. I am not aware of any IPR related to this draft. Thanks Santosh On 5/4/16, 7:17 AM, "Thomas Morin"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 >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] 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:bess-boun...@ietf.org] On Behalf Of Giles Heron Sent: Friday, May 06, 2016 4:13 PM To: Thomas Morin; Carl Moberg (camoberg) Cc: bess@ietf.org; draft-shah-bess-l2vpn-y...@tools.ietf.org 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 <thomas.mo...@orange.com> 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 > 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] Poll for adoption: draft-shah-bess-l2vpn-yang
As co-author, I support. I am not aware of IPR related to this draft. Thanks, Maria -- Forwarded message -- From: Thomas Morin <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>> Date: Wed, May 4, 2016 at 10:17 AM Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang To: bess@ietf.org<mailto:bess@ietf.org> Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org<mailto:draft-shah-bess-l2vpn-y...@tools.ietf.org> 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 BESS@ietf.org<mailto: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] Poll for adoption: draft-shah-bess-l2vpn-yang
As co-author, I support. I am not aware of IPR related to this draft. Thanks, Nick Christopher N. “Nick” Del Regno, Fellow Verizon, VZ Labs 700 Hidden Ridge, W02G94 Irving, TX 75038 972-457-5173 -- Forwarded message -- From: Thomas Morin <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>> Date: Wed, May 4, 2016 at 10:17 AM Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang To: bess@ietf.org<mailto:bess@ietf.org> Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org<mailto:draft-shah-bess-l2vpn-y...@tools.ietf.org> 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 BESS@ietf.org<mailto: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] Poll for adoption: draft-shah-bess-l2vpn-yang
Support adoption as WG doc. On 2016-05-04, 10:17 AM, "BESS on behalf of Thomas Morin"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 >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] Poll for adoption: draft-shah-bess-l2vpn-yang
Support as co-author. Not aware of any IPR that applies to this draft. Regards, Reshad. On 2016-05-04, 10:17 AM, "BESS on behalf of Thomas Morin"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 >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] Poll for adoption: draft-shah-bess-l2vpn-yang
Support as co-author. I am not aware of any IPR that applies to this draft. Best regards Jon -Original Message- From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Thomas Morin Sent: 04 May 2016 15:18 To: bess@ietf.org Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang 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 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] Poll for adoption: draft-shah-bess-l2vpn-yang
As a co-author, I support adoption of this draft. I'm not aware of any relevant IPR. Thanks, Helen > -Original Message- > From: Thomas Morin [mailto:thomas.mo...@orange.com] > Sent: Wednesday, May 4, 2016 10:18 AM > To: bess@ietf.org > Cc: draft-shah-bess-l2vpn-y...@tools.ietf.org > Subject: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang > > 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 BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang
Support as co-author. I am not aware of any IPR related to this draft. Regards , Sajjad. -Original Message- From: Shah, Himanshu [mailto:hs...@ciena.com] Sent: Thursday, May 05, 2016 7:49 AM To: Luay Jalil; Thomas Morin Cc: BESS; draft-shah-bess-l2vpn-y...@tools.ietf.org Subject: RE: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang Support as co-author. I am not aware of any IPR that applies to this draft. Himanshu using iPad (so excuse the auto-corrects...) From: BESS [bess-boun...@ietf.org] On Behalf Of Luay Jalil [luayja...@gmail.com] Sent: Thursday, May 05, 2016 6:23 AM To: Thomas Morin Cc: BESS; draft-shah-bess-l2vpn-y...@tools.ietf.org Subject: Re: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang Resending due to mail delivery messages Support as co-author Not aware of any relevant IPR Thanks, Luay On May 4, 2016 9:18 AM, "Thomas Morin" <thomas.mo...@orange.com<mailto:thomas.mo...@orange.com>> 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 BESS@ietf.org<mailto: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] Poll for adoption: draft-shah-bess-l2vpn-yang
Hi, As a co-author, I support this draft. I am not aware of any IPR that applies to this document. Best Regards, Shunwan -邮件原件- 发件人: BESS [mailto:bess-boun...@ietf.org] 代表 Thomas Morin 发送时间: 2016年5月4日 22:18 收件人: bess@ietf.org 抄送: draft-shah-bess-l2vpn-y...@tools.ietf.org 主题: [bess] Poll for adoption: draft-shah-bess-l2vpn-yang 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 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] Poll for adoption: draft-shah-bess-l2vpn-yang
Yes/support On 5/4/16, 7:17 AM, "BESS on behalf of Thomas Morin"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 >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] Poll for adoption: draft-shah-bess-l2vpn-yang
Thomas, I support adopting this as a WG draft, it’s excellent work. Cheers, Andy On Wed, May 4, 2016 at 10:17 AM, Thomas Morinwrote: > 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 > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess