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

2023-08-05 Thread 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] 2nd WG last call for draft-ietf-bess-evpn-virtual-eth-segment-12

2023-08-05 Thread Ali Sajassi (sajassi) 
Hi Folks,

Just FYI – vast majority of changes for this new revision (rev12) have been 
made for clarification purposes including the new paragraph added in section 
5.5. The new paragraph describes fast convergence scenario for existing figure 
5 in this section.

Thanks to IESG for their review and feedback in tidiness of this document and 
specially to John Scudder for his thorough review as usual and valuable 
comments.

Please take a look at the diff below and if you have any questions/comments wrt 
new edits, please let us know:

https://author-tools.ietf.org/iddiff?url1=draft-ietf-bess-evpn-virtual-eth-segment-11=draft-ietf-bess-evpn-virtual-eth-segment-12=--html

Regards,
Ali

From: BESS  on behalf of Matthew Bocci (Nokia) 

Date: Wednesday, August 2, 2023 at 6:20 AM
To: bess@ietf.org 
Cc: bess-cha...@ietf.org 
Subject: [bess] 2nd WG last call for draft-ietf-bess-evpn-virtual-eth-segment-12
This email begins a two-week working group last call on 
draft-ietf-bess-evpn-virtual-eth-segment-12 
(draft-ietf-bess-evpn-virtual-eth-segment-12 - EVPN Virtual Ethernet 
Segment)

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

The primary purpose of this second last call is to double check that updates 
following AD review of the previous version of the draft did not change the 
meaning of the text, given that there are a number of known implementations of 
the draft. Please pay special attention to the changes which you can see using 
the diff tool on the history page of the datatracker.

This WG LC ends on Wednesday 16th August 2023.

Thanks

Matthew

___
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

2023-08-05 Thread 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