[bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Gyan Mishra]

Dear BESS WG,

*From my presentation today discussion on "merging" of drafts I  would like
to poll the BESS WG on merging of the two drafts labeled #1 & #2 below into
the WG document labeled #3 below:*
*Please respond  to this email.*

*Some history:*
*IPv6 Only PE design / ALL SAFI:*
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft
with Cisco, Juniper, Nokia, Arista, Huawei) *(WG document)*
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New
Draft) - Extended Standards Track to support ALL IPv4 SAFI

*IPv4 Only PE design / ALL SAFI:*
The below drafts were two separate drafts but I have combined into single
draft since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with
Cisco, Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New
Draft) - Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts
have been combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across
all vendors and within same vendor platform -afi/safi matrix to be added to
merged draft)

*Combine these two drafts --> So now we are left with  these 2 new drafts
that extend to support ALL SAFI*

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

*Into WG document below:*

*#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)*

*And make the new combined draft "Standards Track" as it will have the
operational process and procedure update for the alternative dual stacking
method for all SAFI *
*as well as New IANA capability code point for IPv4 next hop encoding
similar to RFC 8950. *

*NEW DRAFT NAME: *

* draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)*

*Why combine?*

   - Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts
   of single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4
   & v6 prefixes being POC tested - can now be done in parallel
   - Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design
   extends to the same set of ALL IPv4 / IPv6 SAFI's
   - Saves both WG time on progressing 3 separate drafts
   - Single draft that has the entire v4 / v6 design & architecture in one
   spot versus being broken out into separate drafts added complexity


Thank you



*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mis...@verizon.com *



*M 301 502-1347*
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Linda Dunbar]

Support the merging of those drafts.

Linda Dunbar

From: BESS  On Behalf Of Gyan Mishra
Sent: Thursday, July 27, 2023 5:32 PM
To: BESS ; bess-cha...@ietf.org; Dongjie (Jimmy) 

Subject: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL 
SAFI Supported

Dear BESS WG,

>From my presentation today discussion on "merging" of drafts I  would like to 
>poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the 
>WG document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Ketan Talaulikar]

Hi Gyan,

Thanks a lot for acting on this feedback from myself and others in the WG.
This is really helpful and will benefit readers of the document but also
through the IETF process all the reviewers and contributors.

With this merge, I hope you are able to consolidate and simplify these
various design options and illustrate the similarities.

I support this merge.

Thanks,
Ketan


On Thu, Jul 27, 2023 at 5:32 PM Gyan Mishra  wrote:

> Dear BESS WG,
>
> *From my presentation today discussion on "merging" of drafts I  would
> like to poll the BESS WG on merging of the two drafts labeled #1 & #2 below
> into the WG document labeled #3 below:*
> *Please respond  to this email.*
>
> *Some history:*
> *IPv6 Only PE design / ALL SAFI:*
> draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft
> with Cisco, Juniper, Nokia, Arista, Huawei) *(WG document)*
> IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
> draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New
> Draft) - Extended Standards Track to support ALL IPv4 SAFI
>
> *IPv4 Only PE design / ALL SAFI:*
> The below drafts were two separate drafts but I have combined into single
> draft since they both were not WG documents
> draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with
> Cisco, Juniper, Nokia, Arista, Huawei)
> IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
> draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New
> Draft) - Extended Standards Track to support ALL IPv4 SAFI (Both v4
> drafts have been combined into this Draft early this year)
> (Introduces new IPv4 next hop encoding IANA capability codepoint
> standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped
> IPv6 address next hop ::::1.1.1.1)
> (Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop
> across all vendors and within same vendor platform -afi/safi matrix to be
> added to merged draft)
>
> *Combine these two drafts --> So now we are left with  these 2 new drafts
> that extend to support ALL SAFI*
>
> #1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
> #2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)
>
> *Into WG document below:*
>
> *#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)*
>
> *And make the new combined draft "Standards Track" as it will have the
> operational process and procedure update for the alternative dual stacking
> method for all SAFI *
> *as well as New IANA capability code point for IPv4 next hop encoding
> similar to RFC 8950. *
>
> *NEW DRAFT NAME: *
>
> * draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)*
>
> *Why combine?*
>
>- Both IPv4 Only PE Design & IPv6 Only PE design are identical
>concepts of single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129
>for both v4 & v6 prefixes being POC tested - can now be done in parallel
>- Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design
>extends to the same set of ALL IPv4 / IPv6 SAFI's
>- Saves both WG time on progressing 3 separate drafts
>- Single draft that has the entire v4 / v6 design & architecture in
>one spot versus being broken out into separate drafts added complexity
>
>
> Thank you
>
> 
>
> *Gyan Mishra*
>
> *Network Solutions A**rchitect *
>
> *Email gyan.s.mis...@verizon.com *
>
>
>
> *M 301 502-1347*
>
> ___
> 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] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Gyan Mishra]

Thanks Ketan

Yes this Will tremendously simplify the design options and all the
redundant information spread across many drafts.

Gyan
On Fri, Jul 28, 2023 at 10:39 AM Ketan Talaulikar 
wrote:

> Hi Gyan,
>
> Thanks a lot for acting on this feedback from myself and others in the WG.
> This is really helpful and will benefit readers of the document but also
> through the IETF process all the reviewers and contributors.
>
> With this merge, I hope you are able to consolidate and simplify these
> various design options and illustrate the similarities.
>
> I support this merge.
>
> Thanks,
> Ketan
>
>
> On Thu, Jul 27, 2023 at 5:32 PM Gyan Mishra  wrote:
>
>> Dear BESS WG,
>>
>> *From my presentation today discussion on "merging" of drafts I  would
>> like to poll the BESS WG on merging of the two drafts labeled #1 & #2 below
>> into the WG document labeled #3 below:*
>> *Please respond  to this email.*
>>
>> *Some history:*
>> *IPv6 Only PE design / ALL SAFI:*
>> draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft
>> with Cisco, Juniper, Nokia, Arista, Huawei) *(WG document)*
>> IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
>> draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New
>> Draft) - Extended Standards Track to support ALL IPv4 SAFI
>>
>> *IPv4 Only PE design / ALL SAFI:*
>> The below drafts were two separate drafts but I have combined into single
>> draft since they both were not WG documents
>> draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with
>> Cisco, Juniper, Nokia, Arista, Huawei)
>> IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
>> draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New
>> Draft) - Extended Standards Track to support ALL IPv4 SAFI (Both v4
>> drafts have been combined into this Draft early this year)
>> (Introduces new IPv4 next hop encoding IANA capability codepoint
>> standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped
>> IPv6 address next hop ::::1.1.1.1)
>> (Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop
>> across all vendors and within same vendor platform -afi/safi matrix to be
>> added to merged draft)
>>
>> *Combine these two drafts --> So now we are left with  these 2 new drafts
>> that extend to support ALL SAFI*
>>
>> #1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
>> #2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)
>>
>> *Into WG document below:*
>>
>> *#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)*
>>
>> *And make the new combined draft "Standards Track" as it will have the
>> operational process and procedure update for the alternative dual stacking
>> method for all SAFI *
>> *as well as New IANA capability code point for IPv4 next hop encoding
>> similar to RFC 8950. *
>>
>> *NEW DRAFT NAME: *
>>
>> * draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)*
>>
>> *Why combine?*
>>
>>- Both IPv4 Only PE Design & IPv6 Only PE design are identical
>>concepts of single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129
>>for both v4 & v6 prefixes being POC tested - can now be done in parallel
>>- Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design
>>extends to the same set of ALL IPv4 / IPv6 SAFI's
>>- Saves both WG time on progressing 3 separate drafts
>>- Single draft that has the entire v4 / v6 design & architecture in
>>one spot versus being broken out into separate drafts added complexity
>>
>>
>> Thank you
>>
>> 
>>
>> *Gyan Mishra*
>>
>> *Network Solutions A**rchitect *
>>
>> *Email gyan.s.mis...@verizon.com *
>>
>>
>>
>> *M 301 502-1347*
>>
>> ___
>> BESS mailing list
>> BESS@ietf.org
>> https://www.ietf.org/mailman/listinfo/bess
>>
> --



*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mis...@verizon.com *



*M 301 502-1347*
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Jeffrey (Zhaohui) Zhang]

I support the merge.



Juniper Business Use Only
From: BESS  On Behalf Of Gyan Mishra
Sent: Thursday, July 27, 2023 5:32 PM
To: BESS ; bess-cha...@ietf.org; Dongjie (Jimmy) 

Subject: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL 
SAFI Supported

[External Email. Be cautious of content]

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to 
poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG 
document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<https://urldefense.com/v3/__http:/www.verizon.com/__;!!NEt6yMaO-gk!C8arvSCr5PtD2Gpn9ns-dG9YtKjEWJiGevRQsEoaM9hrYaWq_mgHCd7DBVpkYt02j0OpQZPT6q8ZSpw66Xqfiw$>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Jingrong Xie]

Hi WG,

I support the merge of these drafts into a whole one.
It will be useful for the PE-CE to use a single address-family BGP session  for 
operation simplicity while supporting Dual-stack services.
Thanks the authors for the great efforts on this work.

Jingrong

本邮件及其附件可能含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
This e-mail and its attachments may contain confidential information from 
HUAWEI, which is intended only for the person or entity whose address is listed 
above. Any use of the information contained herein in any way (including, but 
not limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Gyan Mishra
Sent: Friday, July 28, 2023 8:32 AM
To: BESS ; bess-cha...@ietf.org; Dongjie (Jimmy) 

Subject: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL 
SAFI Supported

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to 
poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG 
document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[图像已被发件人删除。]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Jorge Rabadan (Nokia)]

Hi,

I fully support merging those drafts.
Thanks.
Jorge

From: BESS  on behalf of Gyan Mishra 

Date: Thursday, July 27, 2023 at 5:32 PM
To: BESS , bess-cha...@ietf.org , Dongjie 
(Jimmy) 
Subject: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL 
SAFI Supported

CAUTION: This is an external email. Please be very careful when clicking links 
or opening attachments. See the URL nok.it/ext for additional information.


Dear BESS WG,

>From my presentation today discussion on "merging" of drafts I  would like to 
>poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the 
>WG document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?
· Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts 
of single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & 
v6 prefixes being POC tested - can now be done in parallel
· Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
· Saves both WG time on progressing 3 separate drafts
· Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Dongjie (Jimmy)]

Hi WG,

I support the merge of these documents. This is useful work, and hope this 
would simplify both the design options and the IETF process.

Best regards,
Jie

From: Gyan Mishra 
Sent: Friday, July 28, 2023 8:32 AM
To: BESS ; bess-cha...@ietf.org; Dongjie (Jimmy) 

Subject: IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI 
Supported

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to 
poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG 
document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[图像已被发件人删除。]

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Sudha Madhavi]

Hi BESS-Chairs,

I support merging of drafts as described below by Gyan.

Thank you!!
Sudha


Juniper Business Use Only

-- Forwarded message -
From: Gyan Mishra mailto:hayabusa...@gmail.com>>
Date: Thu, Jul 27, 2023 at 8:31 PM
Subject: IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI 
Supported
To: BESS mailto:bess@ietf.org>>, 
mailto:bess-cha...@ietf.org>>, Dongjie (Jimmy) 
mailto:jie.d...@huawei.com>>

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to 
poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG 
document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com

M 301 502-1347



--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Chenshuanglong]

Hi WG

As a co-author,  I support merging these files. This is a useful work, which 
will help focus on the discussion and simplify the design.

Best Regards
Shuanglong

From: BESS  On Behalf Of Gyan Mishra
Sent: Friday, July 28, 2023 8:32 AM
To: BESS ; bess-cha...@ietf.org; Dongjie (Jimmy) 

Subject: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL 
SAFI Supported

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to 
poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG 
document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Jeff Tantsura]

As co-author I support the merge of the documents proposed, please do provide any objections you might have.Cheers,JeffOn Jul 27, 2023, at 17:32, Gyan Mishra  wrote:Dear BESS WG,From my presentation today discussion on "merging" of drafts I  would like to poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG document labeled #3 below:Please respond  to this email.Some history:IPv6 Only PE design / ALL SAFI:draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with Cisco, Juniper, Nokia, Arista, Huawei) (WG document)IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129 draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) - Extended Standards Track to support ALL IPv4 SAFIIPv4 Only PE design / ALL SAFI:The below drafts were two separate drafts but I have combined into single draft since they both were not WG documentsdraft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, Juniper, Nokia, Arista, Huawei)IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) - Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been combined into this Draft early this year) (Introduces new IPv4 next hop encoding IANA capability codepoint standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped IPv6 address next hop ::::1.1.1.1)(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all vendors and within same vendor platform -afi/safi matrix to be added to merged draft)Combine these two drafts --> So now we are left with  these 2 new drafts that extend to support ALL SAFI#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)Into WG document below:#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)And make the new combined draft "Standards Track" as it will have the operational process and procedure update for the alternative dual stacking method for all SAFI as well as New IANA capability code point for IPv4 next hop encoding similar to RFC 8950.  NEW DRAFT NAME:  draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)Why combine?Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 prefixes being POC tested - can now be done in parallelExtensibility of both the IPv4 Only PE Design & IPv6 Only PE design extends to the same set of ALL IPv4 / IPv6 SAFI'sSaves both WG time on progressing 3 separate draftsSingle draft that has the entire v4 / v6 design & architecture in one spot versus being broken out into separate drafts added complexityThank youGyan MishraNetwork Solutions Architect Email gyan.s.mis...@verizon.comM 301 502-1347
___BESS mailing listBESS@ietf.orghttps://www.ietf.org/mailman/listinfo/bess___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Dikshit, Saumya]

I support merging of the two drafts.

Regards,
Saumya.

From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Gyan Mishra
Sent: Friday, July 28, 2023 6:02 AM
To: BESS ; bess-cha...@ietf.org; Dongjie (Jimmy) 

Subject: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL 
SAFI Supported

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to 
poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG 
document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[Image removed by sender.]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[MohanaSundari Muthusamy]

Dear BESS WG,

I support merging of the the drafts mentioned below.

Regards,
Mohana



On Thu, Jul 27, 2023 at 5:32 PM Gyan Mishra  wrote:

> Dear BESS WG,
>
> *From my presentation today discussion on "merging" of drafts I  would
> like to poll the BESS WG on merging of the two drafts labeled #1 & #2 below
> into the WG document labeled #3 below:*
> *Please respond  to this email.*
>
> *Some history:*
> *IPv6 Only PE design / ALL SAFI:*
> draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft
> with Cisco, Juniper, Nokia, Arista, Huawei) *(WG document)*
> IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
> draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New
> Draft) - Extended Standards Track to support ALL IPv4 SAFI
>
> *IPv4 Only PE design / ALL SAFI:*
> The below drafts were two separate drafts but I have combined into single
> draft since they both were not WG documents
> draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with
> Cisco, Juniper, Nokia, Arista, Huawei)
> IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
> draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New
> Draft) - Extended Standards Track to support ALL IPv4 SAFI (Both v4
> drafts have been combined into this Draft early this year)
> (Introduces new IPv4 next hop encoding IANA capability codepoint
> standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped
> IPv6 address next hop ::::1.1.1.1)
> (Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop
> across all vendors and within same vendor platform -afi/safi matrix to be
> added to merged draft)
>
> *Combine these two drafts --> So now we are left with  these 2 new drafts
> that extend to support ALL SAFI*
>
> #1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
> #2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)
>
> *Into WG document below:*
>
> *#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)*
>
> *And make the new combined draft "Standards Track" as it will have the
> operational process and procedure update for the alternative dual stacking
> method for all SAFI *
> *as well as New IANA capability code point for IPv4 next hop encoding
> similar to RFC 8950. *
>
> *NEW DRAFT NAME: *
>
> * draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)*
>
> *Why combine?*
>
>- Both IPv4 Only PE Design & IPv6 Only PE design are identical
>concepts of single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129
>for both v4 & v6 prefixes being POC tested - can now be done in parallel
>- Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design
>extends to the same set of ALL IPv4 / IPv6 SAFI's
>- Saves both WG time on progressing 3 separate drafts
>- Single draft that has the entire v4 / v6 design & architecture in
>one spot versus being broken out into separate drafts added complexity
>
>
> Thank you
>
> 
>
> *Gyan Mishra*
>
> *Network Solutions A**rchitect *
>
> *Email gyan.s.mis...@verizon.com *
>
>
>
> *M 301 502-1347*
>
> ___
> 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] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Acee Lindem]

I also support merger of the four documents with identification of common 
procedures. 

Thanks,
Acee

> On Aug 6, 2023, at 21:03, Jeff Tantsura  wrote:
> 
> As co-author I support the merge of the documents proposed, please do provide 
> any objections you might have.
> 
> Cheers,
> Jeff
> 
>> On Jul 27, 2023, at 17:32, Gyan Mishra  wrote:
>> 
>> 
>> Dear BESS WG,
>> 
>> From my presentation today discussion on "merging" of drafts I  would like 
>> to poll the BESS WG on merging of the two drafts labeled #1 & #2 below into 
>> the WG document labeled #3 below:
>> Please respond  to this email.
>> 
>> Some history:
>> IPv6 Only PE design / ALL SAFI:
>> draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft 
>> with Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
>> IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129 
>> draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New 
>> Draft) - Extended Standards Track to support ALL IPv4 SAFI
>> 
>> IPv4 Only PE design / ALL SAFI:
>> The below drafts were two separate drafts but I have combined into single 
>> draft since they both were not WG documents
>> draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with 
>> Cisco, Juniper, Nokia, Arista, Huawei)
>> IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
>> draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New 
>> Draft) - Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts 
>> have been combined into this Draft early this year) 
>> (Introduces new IPv4 next hop encoding IANA capability codepoint 
>> standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
>> IPv6 address next hop ::::1.1.1.1)
>> (Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across 
>> all vendors and within same vendor platform -afi/safi matrix to be added to 
>> merged draft)
>> 
>> Combine these two drafts --> So now we are left with  these 2 new drafts 
>> that extend to support ALL SAFI
>> 
>> #1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
>> #2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)
>> 
>> Into WG document below:
>> 
>> #3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)
>> 
>> And make the new combined draft "Standards Track" as it will have the 
>> operational process and procedure update for the alternative dual stacking 
>> method for all SAFI 
>> as well as New IANA capability code point for IPv4 next hop encoding similar 
>> to RFC 8950.  
>> 
>> NEW DRAFT NAME: 
>> 
>>  draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)
>> 
>> Why combine?
>> Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
>> single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & 
>> v6 prefixes being POC tested - can now be done in parallel
>> Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design extends 
>> to the same set of ALL IPv4 / IPv6 SAFI's
>> Saves both WG time on progressing 3 separate drafts
>> Single draft that has the entire v4 / v6 design & architecture in one spot 
>> versus being broken out into separate drafts added complexity
>> 
>> Thank you
>> 
>>  
>> Gyan Mishra
>> Network Solutions Architect 
>> Email gyan.s.mis...@verizon.com 
>> M 301 502-1347
>> 
>> 
>> ___
>> 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] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Mankamana Mishra (mankamis)]

Support the merger of document.

From: Acee Lindem 
Date: Monday, August 7, 2023 at 6:46 AM
To: Jeff Tantsura 
Cc: Gyan Mishra , BESS , 
bess-cha...@ietf.org , Dongjie (Jimmy) 

Subject: Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design 
ALL SAFI Supported
I also support merger of the four documents with identification of common 
procedures.

Thanks,
Acee


On Aug 6, 2023, at 21:03, Jeff Tantsura  wrote:

As co-author I support the merge of the documents proposed, please do provide 
any objections you might have.

Cheers,
Jeff


On Jul 27, 2023, at 17:32, Gyan Mishra  wrote:

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to 
poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG 
document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[Image removed by sender.]<http://www.verizon.com/>
Gyan Mishra
Network Solutions Architect
Email gyan.s.mis...@verizon.com<mailto:gyan.s.mis...@verizon.com>
M 301 502-1347

___
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] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Haoyu Song]

BESS WG

I support the merge of the documents. Thanks!

Best regards,
Haoyu
-- Forwarded message -
From: Gyan Mishra mailto:hayabusa...@gmail.com>>
Date: Thu, Jul 27, 2023 at 8:31 PM
Subject: IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI 
Supported
To: BESS mailto:bess@ietf.org>>, 
mailto:bess-cha...@ietf.org>>, Dongjie (Jimmy) 
mailto:jie.d...@huawei.com>>

Dear BESS WG,

>From my presentation today discussion on "merging" of drafts I  would like to 
>poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the 
>WG document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com

M 301 502-1347

--

[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com

M 301 502-1347

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

Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

[Matthew Bocci (Nokia)]

WG, Authors

There is consensus to merge the individual drafts into the working group draft.

Given that the working group draft will be expanded in scope, I think it makes 
sense to update the name of the draft as proposed by Gyan, as follows:

draft-ietf-bess-ipv6-only-pe-design-04 -> draft-ietf-bess-v4-v6-pe-all-safi-00


Matthew

From: Gyan Mishra 
Date: Friday, 28 July 2023 at 01:32
To: BESS , bess-cha...@ietf.org , Dongjie 
(Jimmy) 
Subject: IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI 
Supported

CAUTION: This is an external email. Please be very careful when clicking links 
or opening attachments. See the URL nok.it/ext for additional information.


Dear BESS WG,

>From my presentation today discussion on "merging" of drafts I  would like to 
>poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the 
>WG document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with 
Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft 
since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, 
Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) 
- Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been 
combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint 
standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped 
IPv6 address next hop ::::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all 
vendors and within same vendor platform -afi/safi matrix to be added to merged 
draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that 
extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the 
operational process and procedure update for the alternative dual stacking 
method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to 
RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of 
single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 
prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design 
extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one 
spot versus being broken out into separate drafts added complexity

Thank you


[Image removed by sender.]

Gyan Mishra

Network Solutions Architect

Email gyan.s.mis...@verizon.com

M 301 502-1347

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