Re: [bess] WG adoption and IPR poll for draft-dawra-bess-srv6-services-02

[Gaurav Dawra]

Hi Matthew, Stéphane,

I am not aware of any non-disclosed IPR

Gaurav

Sent from my iPhone

> On Oct 14, 2019, at 6:39 AM, Robert Raszuk  wrote:
> 
> 
> Hi Matthew, Stéphane,
> 
> I’m not aware of any non-disclosed IPR.
> 
> KInd regards,
> Robert.
> 
>> On Fri, Sep 27, 2019 at 1:00 PM Bocci, Matthew (Nokia - GB) 
>>  wrote:
>> Hello,
>> 
>>  
>> 
>> This email begins a two-weeks WG adoption poll for 
>> draft-dawra-bess-srv6-services-02 [1] .
>> 
>>  
>> 
>> Please review the draft and post any comments to the BESS working group list.
>> 
>>  
>> 
>> We are also polling for knowledge of any undisclosed IPR that applies to 
>> this Document, 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 an author or a contributor of this document, please 
>> respond to this email and indicate whether or not you are aware of any 
>> relevant undisclosed IPR, copying the BESS mailing list. The document won't 
>> progress without answers from all the authors and contributors.
>> 
>> Currently, there are no IPR disclosures against this document.
>> 
>>  
>> 
>> If you are not listed as an author or a contributor, then please explicitly 
>> respond only if you are aware of any IPR that has not yet been disclosed in 
>> conformance with IETF rules.
>> 
>>  
>> 
>> This poll for adoption closes on Friday 11th October 2019.  
>> 
>>  
>> 
>> Regards,
>> 
>> Matthew and Stephane
>> 
>>  
>> 
>> [1] https://datatracker.ietf.org/doc/draft-dawra-bess-srv6-services/
>> 
>>  
>> 
>>  
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IPR poll for draft-dawra-bess-srv6-services-02

[Robert Raszuk]

Hi Matthew, Stéphane,

I’m not aware of any non-disclosed IPR.

KInd regards,
Robert.

On Fri, Sep 27, 2019 at 1:00 PM Bocci, Matthew (Nokia - GB) <
matthew.bo...@nokia.com> wrote:

> Hello,
>
>
>
> This email begins a two-weeks WG adoption poll for
> draft-dawra-bess-srv6-services-02 [1] .
>
>
>
> Please review the draft and post any comments to the BESS working group
> list.
>
>
>
> We are also polling for knowledge of any undisclosed IPR that applies to
> this Document, 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 an author or a contributor of this document, please
> respond to this email and indicate whether or not you are aware of any
> relevant undisclosed IPR, copying the BESS mailing list. The document won't
> progress without answers from all the authors and contributors.
>
> Currently, there are no IPR disclosures against this document.
>
>
>
> If you are not listed as an author or a contributor, then please
> explicitly respond only if you are aware of any IPR that has not yet been
> disclosed in conformance with IETF rules.
>
>
>
> This poll for adoption closes on Friday 11th October 2019.
>
>
>
> Regards,
>
> Matthew and Stephane
>
>
>
> [1] https://datatracker.ietf.org/doc/draft-dawra-bess-srv6-services/
>
>
>
>
>
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG adoption and IP poll for draft-snr-bess-pbb-evpn-isid-cmacflush

[slitkows.ietf]

Hi,

 

We have now a consensus to adopt this document. Authors please publish the 
draft using -ietf-.

 

Thanks,

 

From: BESS <  bess-boun...@ietf.org> on behalf of 
Stephane Litkowski <  slitkows.i...@gmail.com>
Date: Thursday, September 19, 2019 at 5:12 AM
To: "  bess@ietf.org" <  
bess@ietf.org>, "  bess-cha...@ietf.org" < 
 bess-cha...@ietf.org>
Subject: [bess] WG adoption and IP poll for 
draft-snr-bess-pbb-evpn-isid-cmacflush

 

Hi,

 

This email begins a two-weeks WG adoption poll for 
draft-snr-bess-pbb-evpn-isid-cmacflush [1]

Please review the draft and post any comments to the BESS working group list.

 

We are also polling for knowledge of any undisclosed IPR that applies to this 
Document, 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 an author or a contributor of this document, please 
respond to this email and indicate whether or not you are aware of any relevant 
undisclosed IPR, copying the BESS mailing list. The document won't progress 
without answers from all the authors and contributors.

Currently, there are no IPR disclosures against this document.

 

If you are not listed as an author or a contributor, then please explicitly 
respond only if you are aware of any IPR that has not yet been disclosed in 
conformance with IETF rules.

 

This poll for adoption closes on 7th October 2019.  

 

Regards,

Stephane and Matthew

 

[1]   
https://datatracker.ietf.org/doc/draft-snr-bess-pbb-evpn-isid-cmacflush/

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

Re: [bess] Resolutions on draft-snr-bess-evpn-loop-protect

[slitkows.ietf]

Hi Folks,

 

Many thanks for these outcomes and resolution.

I’ll add a comment on the datatracker for the loop-protect draft and I’ll 
proceed with the adoption of the isid-cmacflush.

 

 

Stephane

 

From: Ali Sajassi (sajassi)  
Sent: samedi 12 octobre 2019 02:32
To: bess-cha...@ietf.org; bess@ietf.org
Cc: Rabadan, Jorge (Nokia - US/Mountain View) ; Ali 
Sajassi (sajassi) 
Subject: Resolutions on draft-snr-bess-evpn-loop-protect & 

 

 

Hi Stephane, 

 

 

Jorge and I had a meeting to discuss our comments on the following two drafts 
that are going through WG call: 

 

  
https://tools.ietf.org/html/draft-snr-bess-pbb-evpn-isid-cmacflush-06

  
https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/

 

and reached the following resolutions:

 

On isid-cmacflush, we agreed to proceed with this draft and since we don’t want 
to have two separate solutions for I-SID flushing in PBB-EVPN, we decided to 
remove the section on I-SID flushing in virtual-eth-segment. The main factor 
for this decision was the fact that isid-cmacflush draft has been implemented 
by at least one vendor; whereas, the isid flusing section in 
virtual-eth-segment draft has not been implemented by any vendor to best of our 
knowledge even though the draft at large has been implemented by many vendors. 
If any of the co-authors or WG individual has any comment about this, please 
speak up, otherwise we’ll remove the appropriate section.

 

On loop-protect draft, we agreed on holding its WG adoption at this time and 
extend mac mobility in rfc7432bis to cover loops. The main factor for this 
decision was the fact that the detection mechanism for loop-protect draft is 
the same as mac-duplicate detection mechanism in section 15.1 of RFC 7432. So, 
we agreed we can build based on that and add some paragraphs to describe the 
action of loop protection. Once rfc7432bis is out, we would like to encourage 
people to read it and, unless there is feedback against it, the loop-protect 
draft will be abandoned. If there is feedback stating 7432bis is not enough for 
loop protection, at that time we can discuss if the loop-protect draft needs to 
be resumed and extended or if a new draft is needed.

 

Regards,

Ali & Jorge

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