Re: [lisp] LISP Specifications Published!! :-)

[Dino Farinacci <[e-mail]>]

Alvaro wanted to get to the pubsub draft as next to go to standards track. And I suggested that the multicast drafts (6831 and 8378) are stable and should be standards track fi noish the complete set. 

Dino

> On Oct 27, 2022, at 8:32 PM, Xiejingrong (Jingrong) <[e-mail]> wrote:
> 
> Hi Dino,
> 
> Yes, it's a typo and should be RFC 8378.
> Sorry, I haven't seen anything in the list about multicast topic today or back in this month or this year. Can you please provide the link or just tell the plan.
> I have quickly looked at 9299 (informational) and 9300 (Standard) and found both have contents about multicast and have normative references to 6831 & 8378.
> 
> Thanks, 
> Jingrong
> 
> -----Original Message-----
> From: Dino Farinacci [mailto:[e-mail]] 
> Sent: Friday, October 28, 2022 11:11 AM
> To: Xiejingrong (Jingrong) <[e-mail]>
> Cc: Padma Pillay-Esnault <[e-mail]>; Albert Cabellos <[e-mail]>; [e-mail] list <[e-mail]>
> Subject: Re: [lisp] LISP Specifications Published!! :-)
> 
> I just brought that up in the list today. And it’s RFC 8378. I think you may have a typo below. 
> 
> Dino
> 
>> On Oct 27, 2022, at 8:07 PM, Xiejingrong (Jingrong) <[e-mail]> wrote:
>> 
>> Congratulations to everyone !
>> I may be late joining LISP, and apologize in advance if my following question is repeated:
>> Will the LISP multicast RFCs 6831 & 8379 have bis to advance them from Experimental to Standard ?
>> 
>> Thanks,
>> 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!
>> 
>> -----Original Message-----
>> From: lisp [mailto:[e-mail]] On Behalf Of Padma Pillay-Esnault
>> Sent: Sunday, October 23, 2022 11:35 PM
>> To: Dino Farinacci <[e-mail]>
>> Cc: Albert Cabellos <[e-mail]>; [e-mail] list <[e-mail]>
>> Subject: Re: [lisp] LISP Specifications Published!! :-)
>> 
>> Congratulations to Everyone!
>> It was indeed a long process and thanks to everyone involved.
>> 
>> Cheers
>> Padma
>> 
>>>> On Oct 23, 2022, at 07:45, Dino Farinacci <[e-mail]> wrote:
>>> 
>>> A special thanks to you Albert. You were the backbone of this long standing publication process. 
>>> 
>>> Dino
>>> 
>>>>> On Oct 23, 2022, at 2:49 AM, Albert Cabellos <[e-mail]> wrote:
>>>> 
>>>> Congrats to everyone involved! And also thanks for the final push that made this possible
>>>> 
>>>> Albert
>>>> 
>>>>>> On 22 Oct 2022, at 10:56, Luigi Iannone <[e-mail]> wrote:
>>>>> 
>>>>> A nice team work :-)
>>>>> 
>>>>> Congrats all.
>>>>> 
>>>>> L.
>>>>> 
>>>>>>> On 21 Oct 2022, at 06:59, Dino Farinacci <[e-mail]> wrote:
>>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> Now it’s time to pull the Prosecco!
>>>>>> 
>>>>>> Make it a DOC!
>>>>>> 
>>>>>> Dino
>>>>>> 
>>>>>> _______________________________________________
>>>>>> lisp mailing list
>>>>>> [e-mail]
>>>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>>> 
>>>>> _______________________________________________
>>>>> lisp mailing list
>>>>> [e-mail]
>>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>> 
>>> 
>>> _______________________________________________
>>> lisp mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/lisp
>> 
>> _______________________________________________
>> lisp mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/lisp