Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-02-26 Thread Eric C Rosen

I am not aware of any undisclosed IPR relevant to this document.

On 1/21/19 8:06 AM, stephane.litkow...@orange.com wrote:


Hello Working Group,

This email starts a three weeks Working Group Last Call on 
 draft-ietf-bess-nsh-bgp-control-plane [1].


This poll runs until *the 4th of February*.

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. The Document won't progress without 
answers from all the Authors and Contributors.


We have several IPRs already disclosed.

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.


We are also polling for any existing implementation as per [2].

Thank you,

    Stephane & Matthew

[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/


    [2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
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] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-02-26 Thread Stuart Mackie
Support as contributor – I am not aware of any undisclosed IPR.

Stuart
-914 886 2534

From: BESS  on behalf of "stephane.litkow...@orange.com" 

Date: Monday, January 21, 2019 at 5:06 AM
To: "bess@ietf.org" 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane


Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-nsh-bgp-control-plane [1].



This poll runs until *the 4th of February*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew



[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/



[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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


Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane => MISSING your IPR reply

2019-02-26 Thread LINGALA, AVINASH
I am not aware of any IPR related to this document..

-Avinash
​
From: stephane.litkow...@orange.com 
Sent: Tuesday, February 26, 2019 3:40 AM
To: UTTARO, JAMES ; wsmac...@juinper.net; Keyur Patel 
; LINGALA, AVINASH ; Eric C Rosen 
(ero...@juniper.net) 
Subject: FW: WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane => MISSING your IPR reply

Hi,

We are missing your IPR poll reply on this draft.
Could you please reply to the BESS list ? (bess@ietf.org)

Thanks in advance,

Stephane

From: stephane.litkow...@orange.com 
[mailto:stephane.litkow...@orange.com]
Sent: Monday, January 21, 2019 14:06
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane


Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-nsh-bgp-control-plane [1].



This poll runs until *the 4th of February*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew



[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/



[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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


Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane => MISSING your IPR reply

2019-02-26 Thread LINGALA, AVINASH
Support.

-Avinash
​
From: stephane.litkow...@orange.com 
Sent: Tuesday, February 26, 2019 3:40 AM
To: UTTARO, JAMES ; wsmac...@juinper.net; Keyur Patel 
; LINGALA, AVINASH ; Eric C Rosen 
(ero...@juniper.net) 
Subject: FW: WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane => MISSING your IPR reply

Hi,

We are missing your IPR poll reply on this draft.
Could you please reply to the BESS list ? (bess@ietf.org)

Thanks in advance,

Stephane

From: stephane.litkow...@orange.com 
[mailto:stephane.litkow...@orange.com]
Sent: Monday, January 21, 2019 14:06
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane


Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-nsh-bgp-control-plane [1].



This poll runs until *the 4th of February*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew



[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/



[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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


Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-02-18 Thread stephane.litkowski
Hi,

The WGLC has ended.
A new revision of the draft is required based on the discussions.

Authors,

Please publish the new revision, so we can proceed to the next step.

Brgds,


From: Andrew G. Malis [mailto:agma...@gmail.com]
Sent: Monday, January 28, 2019 15:37
To: John E Drake
Cc: Henderickx, Wim (Nokia - BE/Antwerp); LITKOWSKI Stephane OBS/OINIS; 
bess@ietf.org; bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

John,

Thanks, much appreciated.

And for Stephane and Matthew, seeing as I just contributed some text, I'm not 
aware of any IPR associated with this draft.

Cheers,
Andy


On Mon, Jan 28, 2019 at 8:07 AM John E Drake 
mailto:jdr...@juniper.net>> wrote:
Andy,

We’ll add it to the next revision.  Thanks for your help.

Yours Irrespectively,

John

From: Andrew G. Malis mailto:agma...@gmail.com>>
Sent: Sunday, January 27, 2019 11:48 AM
To: John E Drake mailto:jdr...@juniper.net>>
Cc: Henderickx, Wim (Nokia - BE/Antwerp) 
mailto:wim.henderi...@nokia.com>>; 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>; 
bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

John,

Thanks for confirming, that makes me very comfortable with the readability of 
your draft, seeing as I was able to get it right the first time. :-)

I'd like to request the addition of the following text (or similar, feel free 
to edit for readability and/or correctness), after which I'll be happy to 
support publication of the draft.


7.8 Support for MPLS-Encapsulated NSH Packets

[I-D.ietf-mpls-sfc-encapsulation] describes how to transport SFC packets using 
the NSH over an MPLS transport network. Signaling MPLS encapsulation of SFC 
packets using the NSH is also supported by this document by using the "BGP 
Tunnel Encapsulation Attribute Sub-TLV" with the codepoint 10 (representing 
"MPLS Label Stack") from the "BGP Tunnel Encapsulation Attribute Sub-TLVs" 
registry defined in [I-D.ietf-idr-tunnel-encaps], and also using the "SFP 
Traversal With MPLS Label Stack TLV" and the "SPI/SI Representation sub-TLV" 
with bit 0 set and bit 1 cleared.


BTW, draft-ietf-mpls-sfc-encapsulation has already been submitted to the IESG 
for publication, so adding the reference won't add any delay to this draft.

Thanks again,
Andy


On Sun, Jan 27, 2019 at 10:19 AM John E Drake 
mailto:jdr...@juniper.net>> wrote:
Andy,

That sounds right.

Yours Irrespectively,

John

From: Andrew G. Malis mailto:agma...@gmail.com>>
Sent: Friday, January 25, 2019 6:32 PM
To: John E Drake mailto:jdr...@juniper.net>>
Cc: Henderickx, Wim (Nokia - BE/Antwerp) 
mailto:wim.henderi...@nokia.com>>; 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>; 
bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

John,

So, in order to support draft-ietf-mpls-sfc-encapsulation, looking at 
draft-ietf-idr-tunnel-encaps, you would use the value 10 from the "BGP Tunnel 
Encapsulation Attribute Sub-TLVs" registry, and also from your draft use the 
SFP Traversal With MPLS Label Stack TLV and the SPI/SI Representation sub-TLV 
with bit 0 set and bit 1 cleared? I just want to make sure I correctly read the 
details.

Thanks,
Andy

On Tue, Jan 22, 2019 at 1:15 PM John E Drake 
mailto:jdr...@juniper.net>> wrote:
Wim,

The subject draft was designed w/ NSH in mind.  We added an MPLS representation 
of the NSH later, which is the subject of the first draft you referenced, below.

The way the subject draft is written, the representation of the NSH  and the 
type of transport tunnel can change on a hop-by-hop basis at the discretion of 
the selected next-hop SFF.  This is through the use of the encapsulation 
attribute, which gives us a very open-ended framework in which to work.

I think the latter two drafts you referenced, below, are actually supported 
already but what needs to be written down is exactly what an SFF needs to 
advertise in the encapsulation attribute in order to support them.

I would be happy to work on this w/ anyone else who is interested.

Yours Irrespectively,

John

From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of 
Henderickx, Wim (Nokia - BE/Antwerp)
Sent: Tuesday, January 22, 2019 12:00 PM
To: stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>
Cc: bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

I need to get into more details, but the current draft is written with 
draft

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-28 Thread Andrew G. Malis
John,

Thanks, much appreciated.

And for Stephane and Matthew, seeing as I just contributed some text, I'm
not aware of any IPR associated with this draft.

Cheers,
Andy


On Mon, Jan 28, 2019 at 8:07 AM John E Drake  wrote:

> Andy,
>
>
>
> We’ll add it to the next revision.  Thanks for your help.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* Andrew G. Malis 
> *Sent:* Sunday, January 27, 2019 11:48 AM
> *To:* John E Drake 
> *Cc:* Henderickx, Wim (Nokia - BE/Antwerp) ;
> stephane.litkow...@orange.com; bess@ietf.org; bess-cha...@ietf.org
> *Subject:* Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
>
> John,
>
>
>
> Thanks for confirming, that makes me very comfortable with the readability
> of your draft, seeing as I was able to get it right the first time. :-)
>
>
>
> I'd like to request the addition of the following text (or similar, feel
> free to edit for readability and/or correctness), after which I'll be happy
> to support publication of the draft.
>
>
>
>
>
> 7.8 Support for MPLS-Encapsulated NSH Packets
>
>
>
> [I-D.ietf-mpls-sfc-encapsulation] describes how to transport SFC packets
> using the NSH over an MPLS transport network. Signaling MPLS encapsulation
> of SFC packets using the NSH is also supported by this document by using
> the "BGP Tunnel Encapsulation Attribute Sub-TLV" with the codepoint 10
> (representing "MPLS Label Stack") from the "BGP Tunnel Encapsulation
> Attribute Sub-TLVs" registry defined in [I-D.ietf-idr-tunnel-encaps], and
> also using the "SFP Traversal With MPLS Label Stack TLV" and the "SPI/SI
> Representation sub-TLV" with bit 0 set and bit 1 cleared.
>
>
>
>
>
> BTW, draft-ietf-mpls-sfc-encapsulation has already been submitted to the
> IESG for publication, so adding the reference won't add any delay to this
> draft.
>
>
>
> Thanks again,
>
> Andy
>
>
>
>
>
> On Sun, Jan 27, 2019 at 10:19 AM John E Drake  wrote:
>
> Andy,
>
>
>
> That sounds right.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* Andrew G. Malis 
> *Sent:* Friday, January 25, 2019 6:32 PM
> *To:* John E Drake 
> *Cc:* Henderickx, Wim (Nokia - BE/Antwerp) ;
> stephane.litkow...@orange.com; bess@ietf.org; bess-cha...@ietf.org
> *Subject:* Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
>
> John,
>
>
>
> So, in order to support draft-ietf-mpls-sfc-encapsulation, looking
> at draft-ietf-idr-tunnel-encaps, you would use the value 10 from the "BGP
> Tunnel Encapsulation Attribute Sub-TLVs" registry, and also from your draft
> use the SFP Traversal With MPLS Label Stack TLV and the SPI/SI
> Representation sub-TLV with bit 0 set and bit 1 cleared? I just want to
> make sure I correctly read the details.
>
>
>
> Thanks,
>
> Andy
>
>
>
> On Tue, Jan 22, 2019 at 1:15 PM John E Drake  wrote:
>
> Wim,
>
>
>
> The subject draft was designed w/ NSH in mind.  We added an MPLS
> representation of the NSH later, which is the subject of the first draft
> you referenced, below.
>
>
>
> The way the subject draft is written, the representation of the NSH  and
> the type of transport tunnel can change on a hop-by-hop basis at the
> discretion of the selected next-hop SFF.  This is through the use of the
> encapsulation attribute, which gives us a very open-ended framework in
> which to work.
>
>
>
> I think the latter two drafts you referenced, below, are actually
> supported already but what needs to be written down is exactly what an SFF
> needs to advertise in the encapsulation attribute in order to support
> them.
>
>
>
> I would be happy to work on this w/ anyone else who is interested.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* BESS  *On Behalf Of *Henderickx, Wim
> (Nokia - BE/Antwerp)
> *Sent:* Tuesday, January 22, 2019 12:00 PM
> *To:* stephane.litkow...@orange.com; bess@ietf.org
> *Cc:* bess-cha...@ietf.org
> *Subject:* Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
> I need to get into more details, but the current draft is written with 
> draft-ietf-mpls-sfc-04
> dataplane in mind. I believe that the draft can be useful with other
> dataplanes like: draft-ietf-mpls-sfc-encapsulation and
> draft-guichard-spring-nsh-s
>
> So I would like the see the BGP control plane extensions here to become
> more generic to support multiple data-planes options

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-28 Thread John E Drake
Andy,

We’ll add it to the next revision.  Thanks for your help.

Yours Irrespectively,

John

From: Andrew G. Malis 
Sent: Sunday, January 27, 2019 11:48 AM
To: John E Drake 
Cc: Henderickx, Wim (Nokia - BE/Antwerp) ; 
stephane.litkow...@orange.com; bess@ietf.org; bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

John,

Thanks for confirming, that makes me very comfortable with the readability of 
your draft, seeing as I was able to get it right the first time. :-)

I'd like to request the addition of the following text (or similar, feel free 
to edit for readability and/or correctness), after which I'll be happy to 
support publication of the draft.


7.8 Support for MPLS-Encapsulated NSH Packets

[I-D.ietf-mpls-sfc-encapsulation] describes how to transport SFC packets using 
the NSH over an MPLS transport network. Signaling MPLS encapsulation of SFC 
packets using the NSH is also supported by this document by using the "BGP 
Tunnel Encapsulation Attribute Sub-TLV" with the codepoint 10 (representing 
"MPLS Label Stack") from the "BGP Tunnel Encapsulation Attribute Sub-TLVs" 
registry defined in [I-D.ietf-idr-tunnel-encaps], and also using the "SFP 
Traversal With MPLS Label Stack TLV" and the "SPI/SI Representation sub-TLV" 
with bit 0 set and bit 1 cleared.


BTW, draft-ietf-mpls-sfc-encapsulation has already been submitted to the IESG 
for publication, so adding the reference won't add any delay to this draft.

Thanks again,
Andy


On Sun, Jan 27, 2019 at 10:19 AM John E Drake 
mailto:jdr...@juniper.net>> wrote:
Andy,

That sounds right.

Yours Irrespectively,

John

From: Andrew G. Malis mailto:agma...@gmail.com>>
Sent: Friday, January 25, 2019 6:32 PM
To: John E Drake mailto:jdr...@juniper.net>>
Cc: Henderickx, Wim (Nokia - BE/Antwerp) 
mailto:wim.henderi...@nokia.com>>; 
stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>; 
bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

John,

So, in order to support draft-ietf-mpls-sfc-encapsulation, looking at 
draft-ietf-idr-tunnel-encaps, you would use the value 10 from the "BGP Tunnel 
Encapsulation Attribute Sub-TLVs" registry, and also from your draft use the 
SFP Traversal With MPLS Label Stack TLV and the SPI/SI Representation sub-TLV 
with bit 0 set and bit 1 cleared? I just want to make sure I correctly read the 
details.

Thanks,
Andy

On Tue, Jan 22, 2019 at 1:15 PM John E Drake 
mailto:jdr...@juniper.net>> wrote:
Wim,

The subject draft was designed w/ NSH in mind.  We added an MPLS representation 
of the NSH later, which is the subject of the first draft you referenced, below.

The way the subject draft is written, the representation of the NSH  and the 
type of transport tunnel can change on a hop-by-hop basis at the discretion of 
the selected next-hop SFF.  This is through the use of the encapsulation 
attribute, which gives us a very open-ended framework in which to work.

I think the latter two drafts you referenced, below, are actually supported 
already but what needs to be written down is exactly what an SFF needs to 
advertise in the encapsulation attribute in order to support them.

I would be happy to work on this w/ anyone else who is interested.

Yours Irrespectively,

John

From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of 
Henderickx, Wim (Nokia - BE/Antwerp)
Sent: Tuesday, January 22, 2019 12:00 PM
To: stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>
Cc: bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

I need to get into more details, but the current draft is written with 
draft-ietf-mpls-sfc-04 dataplane in mind. I believe that the draft can be 
useful with other dataplanes like: draft-ietf-mpls-sfc-encapsulation and 
draft-guichard-spring-nsh-s
So I would like the see the BGP control plane extensions here to become more 
generic to support multiple data-planes options. I need to go in more detail, 
but from high level this is my feedback here. I don’t want to stop/block this 
work as I believe this is a very useful proposal, but if we make it more 
generic it can serve a bigger purpose.

So I would like to see the following:

  1.  Protocol draft
  2.  Use case drafts for the different data planes.

My 2 cents.

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
Stephane Litkowski 
mailto:stephane.litkow...@orange.com>>
Date: Monday, 21 January 2019 at 08:06
To: "bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-27 Thread Andrew G. Malis
John,

Thanks for confirming, that makes me very comfortable with the readability
of your draft, seeing as I was able to get it right the first time. :-)

I'd like to request the addition of the following text (or similar, feel
free to edit for readability and/or correctness), after which I'll be happy
to support publication of the draft.


7.8 Support for MPLS-Encapsulated NSH Packets

[I-D.ietf-mpls-sfc-encapsulation] describes how to transport SFC packets
using the NSH over an MPLS transport network. Signaling MPLS encapsulation
of SFC packets using the NSH is also supported by this document by using
the "BGP Tunnel Encapsulation Attribute Sub-TLV" with the codepoint 10
(representing "MPLS Label Stack") from the "BGP Tunnel Encapsulation
Attribute Sub-TLVs" registry defined in [I-D.ietf-idr-tunnel-encaps], and
also using the "SFP Traversal With MPLS Label Stack TLV" and the "SPI/SI
Representation sub-TLV" with bit 0 set and bit 1 cleared.


BTW, draft-ietf-mpls-sfc-encapsulation has already been submitted to the
IESG for publication, so adding the reference won't add any delay to this
draft.

Thanks again,
Andy


On Sun, Jan 27, 2019 at 10:19 AM John E Drake  wrote:

> Andy,
>
>
>
> That sounds right.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* Andrew G. Malis 
> *Sent:* Friday, January 25, 2019 6:32 PM
> *To:* John E Drake 
> *Cc:* Henderickx, Wim (Nokia - BE/Antwerp) ;
> stephane.litkow...@orange.com; bess@ietf.org; bess-cha...@ietf.org
> *Subject:* Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
>
> John,
>
>
>
> So, in order to support draft-ietf-mpls-sfc-encapsulation, looking
> at draft-ietf-idr-tunnel-encaps, you would use the value 10 from the "BGP
> Tunnel Encapsulation Attribute Sub-TLVs" registry, and also from your draft
> use the SFP Traversal With MPLS Label Stack TLV and the SPI/SI
> Representation sub-TLV with bit 0 set and bit 1 cleared? I just want to
> make sure I correctly read the details.
>
>
>
> Thanks,
>
> Andy
>
>
>
> On Tue, Jan 22, 2019 at 1:15 PM John E Drake  wrote:
>
> Wim,
>
>
>
> The subject draft was designed w/ NSH in mind.  We added an MPLS
> representation of the NSH later, which is the subject of the first draft
> you referenced, below.
>
>
>
> The way the subject draft is written, the representation of the NSH  and
> the type of transport tunnel can change on a hop-by-hop basis at the
> discretion of the selected next-hop SFF.  This is through the use of the
> encapsulation attribute, which gives us a very open-ended framework in
> which to work.
>
>
>
> I think the latter two drafts you referenced, below, are actually
> supported already but what needs to be written down is exactly what an SFF
> needs to advertise in the encapsulation attribute in order to support
> them.
>
>
>
> I would be happy to work on this w/ anyone else who is interested.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* BESS  *On Behalf Of *Henderickx, Wim
> (Nokia - BE/Antwerp)
> *Sent:* Tuesday, January 22, 2019 12:00 PM
> *To:* stephane.litkow...@orange.com; bess@ietf.org
> *Cc:* bess-cha...@ietf.org
> *Subject:* Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
> I need to get into more details, but the current draft is written with 
> draft-ietf-mpls-sfc-04
> dataplane in mind. I believe that the draft can be useful with other
> dataplanes like: draft-ietf-mpls-sfc-encapsulation and
> draft-guichard-spring-nsh-s
>
> So I would like the see the BGP control plane extensions here to become
> more generic to support multiple data-planes options. I need to go in more
> detail, but from high level this is my feedback here. I don’t want to
> stop/block this work as I believe this is a very useful proposal, but if we
> make it more generic it can serve a bigger purpose.
>
>
>
> So I would like to see the following:
>
>1. Protocol draft
>2. Use case drafts for the different data planes.
>
>
>
> My 2 cents.
>
>
>
> *From: *BESS  on behalf of Stephane Litkowski <
> stephane.litkow...@orange.com>
> *Date: *Monday, 21 January 2019 at 08:06
> *To: *"bess@ietf.org" 
> *Cc: *"bess-cha...@ietf.org" 
> *Subject: *[bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
>
> Hello Working Group,
>
>
>
> This email starts a three weeks Working Group Last Call on
>  draft-ietf-bess-nsh-bgp-control-plane [1].
>
>
>
> This poll runs until *the 4th of February*.
>

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-27 Thread John E Drake
Andy,

That sounds right.

Yours Irrespectively,

John

From: Andrew G. Malis 
Sent: Friday, January 25, 2019 6:32 PM
To: John E Drake 
Cc: Henderickx, Wim (Nokia - BE/Antwerp) ; 
stephane.litkow...@orange.com; bess@ietf.org; bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

John,

So, in order to support draft-ietf-mpls-sfc-encapsulation, looking at 
draft-ietf-idr-tunnel-encaps, you would use the value 10 from the "BGP Tunnel 
Encapsulation Attribute Sub-TLVs" registry, and also from your draft use the 
SFP Traversal With MPLS Label Stack TLV and the SPI/SI Representation sub-TLV 
with bit 0 set and bit 1 cleared? I just want to make sure I correctly read the 
details.

Thanks,
Andy

On Tue, Jan 22, 2019 at 1:15 PM John E Drake 
mailto:jdr...@juniper.net>> wrote:
Wim,

The subject draft was designed w/ NSH in mind.  We added an MPLS representation 
of the NSH later, which is the subject of the first draft you referenced, below.

The way the subject draft is written, the representation of the NSH  and the 
type of transport tunnel can change on a hop-by-hop basis at the discretion of 
the selected next-hop SFF.  This is through the use of the encapsulation 
attribute, which gives us a very open-ended framework in which to work.

I think the latter two drafts you referenced, below, are actually supported 
already but what needs to be written down is exactly what an SFF needs to 
advertise in the encapsulation attribute in order to support them.

I would be happy to work on this w/ anyone else who is interested.

Yours Irrespectively,

John

From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of 
Henderickx, Wim (Nokia - BE/Antwerp)
Sent: Tuesday, January 22, 2019 12:00 PM
To: stephane.litkow...@orange.com<mailto:stephane.litkow...@orange.com>; 
bess@ietf.org<mailto:bess@ietf.org>
Cc: bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

I need to get into more details, but the current draft is written with 
draft-ietf-mpls-sfc-04 dataplane in mind. I believe that the draft can be 
useful with other dataplanes like: draft-ietf-mpls-sfc-encapsulation and 
draft-guichard-spring-nsh-s
So I would like the see the BGP control plane extensions here to become more 
generic to support multiple data-planes options. I need to go in more detail, 
but from high level this is my feedback here. I don’t want to stop/block this 
work as I believe this is a very useful proposal, but if we make it more 
generic it can serve a bigger purpose.

So I would like to see the following:

  1.  Protocol draft
  2.  Use case drafts for the different data planes.

My 2 cents.

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
Stephane Litkowski 
mailto:stephane.litkow...@orange.com>>
Date: Monday, 21 January 2019 at 08:06
To: "bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>" 
mailto:bess-cha...@ietf.org>>
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane


Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-nsh-bgp-control-plane [1].



This poll runs until *the 4th of February*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew



[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Dnsh-2Dbgp-2Dcontrol-2Dplane_=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE=NmtJTnm15eI5V8pM4BEFevbruNYPMxijWj6csDXLze8=TfgMeOz6kzVSiGyw-h1RMGo9QIYi6K9bz8AcyCd3BNI=>



[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=CRB2tJiQePk0cT-h5LGhEW

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-25 Thread Andrew G. Malis
John,

So, in order to support draft-ietf-mpls-sfc-encapsulation, looking
at draft-ietf-idr-tunnel-encaps, you would use the value 10 from the "BGP
Tunnel Encapsulation Attribute Sub-TLVs" registry, and also from your draft
use the SFP Traversal With MPLS Label Stack TLV and the SPI/SI
Representation sub-TLV with bit 0 set and bit 1 cleared? I just want to
make sure I correctly read the details.

Thanks,
Andy

On Tue, Jan 22, 2019 at 1:15 PM John E Drake  wrote:

> Wim,
>
>
>
> The subject draft was designed w/ NSH in mind.  We added an MPLS
> representation of the NSH later, which is the subject of the first draft
> you referenced, below.
>
>
>
> The way the subject draft is written, the representation of the NSH  and
> the type of transport tunnel can change on a hop-by-hop basis at the
> discretion of the selected next-hop SFF.  This is through the use of the
> encapsulation attribute, which gives us a very open-ended framework in
> which to work.
>
>
>
> I think the latter two drafts you referenced, below, are actually
> supported already but what needs to be written down is exactly what an SFF
> needs to advertise in the encapsulation attribute in order to support
> them.
>
>
>
> I would be happy to work on this w/ anyone else who is interested.
>
>
>
> Yours Irrespectively,
>
>
>
> John
>
>
>
> *From:* BESS  *On Behalf Of * Henderickx, Wim
> (Nokia - BE/Antwerp)
> *Sent:* Tuesday, January 22, 2019 12:00 PM
> *To:* stephane.litkow...@orange.com; bess@ietf.org
> *Cc:* bess-cha...@ietf.org
> *Subject:* Re: [bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
> I need to get into more details, but the current draft is written with 
> draft-ietf-mpls-sfc-04
> dataplane in mind. I believe that the draft can be useful with other
> dataplanes like: draft-ietf-mpls-sfc-encapsulation and
> draft-guichard-spring-nsh-s
>
> So I would like the see the BGP control plane extensions here to become
> more generic to support multiple data-planes options. I need to go in more
> detail, but from high level this is my feedback here. I don’t want to
> stop/block this work as I believe this is a very useful proposal, but if we
> make it more generic it can serve a bigger purpose.
>
>
>
> So I would like to see the following:
>
>1. Protocol draft
>2. Use case drafts for the different data planes.
>
>
>
> My 2 cents.
>
>
>
> *From: *BESS  on behalf of Stephane Litkowski <
> stephane.litkow...@orange.com>
> *Date: *Monday, 21 January 2019 at 08:06
> *To: *"bess@ietf.org" 
> *Cc: *"bess-cha...@ietf.org" 
> *Subject: *[bess] WGLC, IPR and implementation poll for
> draft-ietf-bess-nsh-bgp-control-plane
>
>
>
> Hello Working Group,
>
>
>
> This email starts a three weeks Working Group Last Call on
>  draft-ietf-bess-nsh-bgp-control-plane [1].
>
>
>
> This poll runs until *the 4th of February*.
>
>
>
> 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. The Document won't progress without answers from
> all the Authors and Contributors.
>
>
>
> We have several IPRs already disclosed.
>
>
>
> 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.
>
>
>
> We are also polling for any existing implementation as per [2].
>
>
>
> Thank you,
>
> Stephane & Matthew
>
>
>
> [1]
> https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Dnsh-2Dbgp-2Dcontrol-2Dplane_=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE=NmtJTnm15eI5V8pM4BEFevbruNYPMxijWj6csDXLze8=TfgMeOz6kzVSiGyw-h1RMGo9QIYi6K9bz8AcyCd3BNI=>
>
>
>
> [2]
> https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE=NmtJTnm15eI5V8pM4BEFevbruNYPMxijWj6csDXLze8=hHwZCKH4zzsnENDFhTn86H9rP-vyWW-Wux-hC7pP6BE=>
>
>
&g

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-23 Thread Adrian Farrel
Hi Stephane,

 

I am not aware of any IPR that has not already been disclosed against this
document.

 

Thanks,

Adrian

 

From: BESS  On Behalf Of
stephane.litkow...@orange.com
Sent: 21 January 2019 13:06
To: bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: [bess] WGLC, IPR and implementation poll for
draft-ietf-bess-nsh-bgp-control-plane

 

Hello Working Group,



This email starts a three weeks Working Group Last Call on
draft-ietf-bess-nsh-bgp-control-plane [1]. 

 

This poll runs until *the 4th of February*.

 

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. The Document won't progress without answers from
all the Authors and Contributors.

 

We have several IPRs already disclosed.

 

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.

 

We are also polling for any existing implementation as per [2]. 



Thank you,

Stephane & Matthew

 

[1]
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/

 

[2]
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

 

 


_
 
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
 
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-23 Thread Luay Jalil
Not aware of any IPR

Support (co-author)

Luay


On Jan 21, 2019 7:06 AM,  wrote:

Hello Working Group,



This email starts a three weeks Working Group Last Call on
 draft-ietf-bess-nsh-bgp-control-plane [1].



This poll runs until *the 4th of February*.



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. The Document won't progress without answers from
all the Authors and Contributors.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew



[1]
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/



[2]
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw





_

Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les
messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere,
deforme ou falsifie. Merci.

This message and its attachments may contain confidential or
privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have
been modified, changed or falsified.
Thank you.

___
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] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-22 Thread Adrian Farrel
Hey Wim,

 

Thanks for (not  ) reading.

 

Yes, MPLS-SFC was certainly in mind, but we wrote the initial document only for 
NSH, and so the document is named for that and fully scoped for that.

 

I believe that draft-ietf-mpls-sfc-encapsulation is “only” an interface 
encapsulation of NSH. Thus if we support NSH (we do, and we describe it), and 
if we support identifying the interface “tunnel type” (we do because this is a 
standard extension for BGP and we talk about it in the draft), I think we have 
that document covered.

 

I haven’t read draft-guichard-spring-nsh-s (yet), but it might be a bit 
premature to include an applicability discussion of that work before it is 
adopted by SPRING.

 

BUT, I certainly have no objection to someone (you?) starting one or more 
applicability documents.

 

Ciao,

Adrian

 

Oh! John just sent almost the same email!

 

From: BESS  On Behalf Of Henderickx, Wim (Nokia - 
BE/Antwerp)
Sent: 22 January 2019 17:00
To: stephane.litkow...@orange.com; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

 


I need to get into more details, but the current draft is written with 
draft-ietf-mpls-sfc-04 dataplane in mind. I believe that the draft can be 
useful with other dataplanes like: draft-ietf-mpls-sfc-encapsulation and 
draft-guichard-spring-nsh-s


So I would like the see the BGP control plane extensions here to become more 
generic to support multiple data-planes options. I need to go in more detail, 
but from high level this is my feedback here. I don’t want to stop/block this 
work as I believe this is a very useful proposal, but if we make it more 
generic it can serve a bigger purpose.

 

So I would like to see the following:

1.  Protocol draft
2.  Use case drafts for the different data planes.

 

My 2 cents.

 

From: BESS mailto:bess-boun...@ietf.org> > on behalf of 
Stephane Litkowski mailto:stephane.litkow...@orange.com> >
Date: Monday, 21 January 2019 at 08:06
To: "bess@ietf.org <mailto:bess@ietf.org> " mailto:bess@ietf.org> >
Cc: "bess-cha...@ietf.org <mailto:bess-cha...@ietf.org> " mailto:bess-cha...@ietf.org> >
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

 

Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-nsh-bgp-control-plane [1]. 

 

This poll runs until *the 4th of February*.

 

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. The Document won't progress without answers from all the 
Authors and Contributors.

 

We have several IPRs already disclosed.

 

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.

 

We are also polling for any existing implementation as per [2]. 



Thank you,

Stephane & Matthew

 

[1] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/

 

[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw

 

 

_
 
Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.
 
This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess


Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-22 Thread John E Drake
Wim,

The subject draft was designed w/ NSH in mind.  We added an MPLS representation 
of the NSH later, which is the subject of the first draft you referenced, below.

The way the subject draft is written, the representation of the NSH  and the 
type of transport tunnel can change on a hop-by-hop basis at the discretion of 
the selected next-hop SFF.  This is through the use of the encapsulation 
attribute, which gives us a very open-ended framework in which to work.

I think the latter two drafts you referenced, below, are actually supported 
already but what needs to be written down is exactly what an SFF needs to 
advertise in the encapsulation attribute in order to support them.

I would be happy to work on this w/ anyone else who is interested.

Yours Irrespectively,

John

From: BESS  On Behalf Of Henderickx, Wim (Nokia - 
BE/Antwerp)
Sent: Tuesday, January 22, 2019 12:00 PM
To: stephane.litkow...@orange.com; bess@ietf.org
Cc: bess-cha...@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane

I need to get into more details, but the current draft is written with 
draft-ietf-mpls-sfc-04 dataplane in mind. I believe that the draft can be 
useful with other dataplanes like: draft-ietf-mpls-sfc-encapsulation and 
draft-guichard-spring-nsh-s
So I would like the see the BGP control plane extensions here to become more 
generic to support multiple data-planes options. I need to go in more detail, 
but from high level this is my feedback here. I don’t want to stop/block this 
work as I believe this is a very useful proposal, but if we make it more 
generic it can serve a bigger purpose.

So I would like to see the following:

  1.  Protocol draft
  2.  Use case drafts for the different data planes.

My 2 cents.

From: BESS mailto:bess-boun...@ietf.org>> on behalf of 
Stephane Litkowski 
mailto:stephane.litkow...@orange.com>>
Date: Monday, 21 January 2019 at 08:06
To: "bess@ietf.org<mailto:bess@ietf.org>" mailto:bess@ietf.org>>
Cc: "bess-cha...@ietf.org<mailto:bess-cha...@ietf.org>" 
mailto:bess-cha...@ietf.org>>
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane


Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-nsh-bgp-control-plane [1].



This poll runs until *the 4th of February*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew



[1] 
https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Dnsh-2Dbgp-2Dcontrol-2Dplane_=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE=NmtJTnm15eI5V8pM4BEFevbruNYPMxijWj6csDXLze8=TfgMeOz6kzVSiGyw-h1RMGo9QIYi6K9bz8AcyCd3BNI=>



[2] 
https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw=DwMGaQ=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE=NmtJTnm15eI5V8pM4BEFevbruNYPMxijWj6csDXLze8=hHwZCKH4zzsnENDFhTn86H9rP-vyWW-Wux-hC7pP6BE=>



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable

Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane

2019-01-22 Thread Henderickx, Wim (Nokia - BE/Antwerp)
I need to get into more details, but the current draft is written with 
draft-ietf-mpls-sfc-04 dataplane in mind. I believe that the draft can be 
useful with other dataplanes like: draft-ietf-mpls-sfc-encapsulation and 
draft-guichard-spring-nsh-s
So I would like the see the BGP control plane extensions here to become more 
generic to support multiple data-planes options. I need to go in more detail, 
but from high level this is my feedback here. I don’t want to stop/block this 
work as I believe this is a very useful proposal, but if we make it more 
generic it can serve a bigger purpose.

So I would like to see the following:

  1.  Protocol draft
  2.  Use case drafts for the different data planes.

My 2 cents.

From: BESS  on behalf of Stephane Litkowski 

Date: Monday, 21 January 2019 at 08:06
To: "bess@ietf.org" 
Cc: "bess-cha...@ietf.org" 
Subject: [bess] WGLC, IPR and implementation poll for 
draft-ietf-bess-nsh-bgp-control-plane


Hello Working Group,



This email starts a three weeks Working Group Last Call on  
draft-ietf-bess-nsh-bgp-control-plane [1].



This poll runs until *the 4th of February*.



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. The Document won't progress without answers from all the 
Authors and Contributors.



We have several IPRs already disclosed.



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.



We are also polling for any existing implementation as per [2].



Thank you,

Stephane & Matthew



[1] https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/



[2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw



_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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