[Idr] Re: IANA Allocation Request for draft-ietf-idr-bgpls-inter-as-topology-ext-16

[linchangwang <[e-mail]>]

Hi Sue,

       I need to check if there are similar implementations in open-source routing.
Currently, we are developing on commercial routers.
As for open-source routing platforms, such as white-box switches based on SONiC, I need to confirm further.


Thanks,
Changwang

发件人: Susan Hares <[e-mail]>
发送时间: 2024年8月2日 21:14
收件人: linchangwang (RD) <[e-mail]>; Acee Lindem <[e-mail]>; Aijun Wang <[e-mail]>
抄送: idr <[e-mail]>; [e-mail]
主题: RE: [Idr] Re: IANA Allocation Request for draft-ietf-idr-bgpls-inter-as-topology-ext-16

Changwang:

Are you planning to test this against an open routing stack (e.g. openbgpd)?

Thank you, Sue

From: linchangwang <[e-mail]<mailto:[e-mail]>>
Sent: Tuesday, July 30, 2024 10:21 PM
To: Acee Lindem <[e-mail]<mailto:[e-mail]>>; Aijun Wang <[e-mail]<mailto:[e-mail]>>
Cc: Susan Hares <[e-mail]<mailto:[e-mail]>>; idr <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: Re: [Idr] Re: IANA Allocation Request for draft-ietf-idr-bgpls-inter-as-topology-ext-16


Hi Acee,

       H3C, as an equipment vendor, is currently in the development phase.
In response to the practical demands of carriers, we encounter such application scenarios.
We need specific TLV definitions from IANA to enable standardized communication with third-party controllers.

Thanks,
Changwang

发件人: Acee Lindem <[e-mail]<mailto:[e-mail]>>
发送时间: 2024年7月31日 1:02
收件人: Aijun Wang <[e-mail]<mailto:[e-mail]>>
抄送: Susan Hares <[e-mail]<mailto:[e-mail]>>; idr <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
主题: [Idr] Re: IANA Allocation Request for draft-ietf-idr-bgpls-inter-as-topology-ext-16

Hi Aijun,

On Jul 29, 2024, at 22:55, Aijun Wang <[e-mail]<mailto:[e-mail]>> wrote:

Hi, John:

Would you like to approve the following IANA allocation request for https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-inter-as-topology-ext/?
We are putting forwarding to the implementations for the protocol extension that defined in this document.

Which implementations are implementing this draft?

Thanks,
Acee




Thanks in advance for your support.

Best Regards

Aijun Wang
China Telecom

发件人: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] 代表 Susan Hares
发送时间: 2024年6月8日 15:23
收件人: John Scudder <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
抄送: [e-mail]<mailto:[e-mail]>
主题: [Idr] IANA Allocation Request for draft-ietf-idr-bgpls-inter-as-topology-ext-16

John:

I am requesting Early allocation for the following assignments from draft-ietf-idr-bgpls-inter-as-topology-ext-16.

From section 10.1.  New BGP-LS NLRI type

   This document defines a new value in the registry "BGP-LS NLRI
   Types":

        Code Point        Description       Assignment Type
   ---------------------- ---------------- ----------------
   |TBD1(suggestion 7)    Stub Link NLRI   Expert Review


10.2.  New Stub Link Descriptors


   This document defines three new values in the registry "BGP-LS NLRI

   and Attribute TLVs":

        Code Point         Description          Assignment Type
   ----------------------  -------------------  ----------------
   TBD2(suggestion 270)    Remote AS Number     Expert Review (256-64999)
   TBD3(suggestion 271)    IPv4 Remote ASBR ID  Expert Review (256-64999)
   TBD4(suggestion 272)    IPv6 Remote ASBR ID  Expert Review (256-64999)


Please confirm that you approve of sending these requests to IANA.

The authors need the assignments for interoperability testing.

Sue Hares
_______________________________________________
Idr mailing list -- [e-mail]<mailto:[e-mail]>
To unsubscribe send an email to [e-mail]<mailto:[e-mail]>

-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from New H3C, 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!