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 <jefftant.ietf@gmail.com> 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 <hayabusagsm@gmail.com> 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 ::FFFF::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.mishra@verizon.com <mailto:gyan.s.mishra@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