Re: [auth48] [C381] AUTH48: RFC-to-be 9306 <draft-ietf-lisp-vendor-lcaf-12> for your review

["Fabio Maino (fmaino)" <[e-mail]>]

Dino, 
I've brought this up with Alanna in the appropriate list. 

It seems an isolate instance, so hopefully she should be able to fix it. 

Thanks,
Fabio

On 9/24/22, 5:28 PM, "Dino Farinacci" <[e-mail]> wrote:

    I am copying this list because I don’t have the distribution list for 9303 (since I’m not listed as an author). 

    I have one comment on 9303. There is a reference to “128-bits-long”. I don’t think it should be hyphenated for these reasons:

    (1) There is nothing distinguished about the word “long”. 

    (2) “long” is redundant with 128-bits just like a “short minute” is a contradiction. 

    (3) It should read either “128-bits in length” or simply “128-bits long”. 

    This should be the case throughout the cluster. Please confirm if this is just an isolated case. 

    Dino

    > On Sep 23, 2022, at 2:52 PM, Alanna Paloma <[e-mail]> wrote:
    > 
    > Hi Authors,
    > 
    > We have updated the affiliation information in the files accordingly.
    > 
    > We will await Vina’s approval prior to moving this document forward in the publication process. 
    > 
    > The files have been posted here (please refresh):
    > https://www.rfc-editor.org/authors/rfc9306.xml
    > https://www.rfc-editor.org/authors/rfc9306.txt
    > https://www.rfc-editor.org/authors/rfc9306.html
    > https://www.rfc-editor.org/authors/rfc9306.pdf
    > 
    > The relevant diff files have been posted here:
    > https://www.rfc-editor.org/authors/rfc9306-diff.html (comprehensive diff)
    > https://www.rfc-editor.org/authors/rfc9306-auth48diff.html (AUTH48 changes)
    > 
    > For the AUTH48 status of this document, please see:
    > https://www.rfc-editor.org/auth48/rfc9306
    > 
    > Thank you,
    > RFC Editor/ap
    > 
    >> On Sep 21, 2022, at 12:29 PM, Alanna Paloma <[e-mail]> wrote:
    >> 
    >> Hi Vrushali,
    >> 
    >> Thank you for your reply. We have noted your approval on the AUTH48 status page:
    >> https://www.rfc-editor.org/auth48/rfc9306
    >> 
    >> Please note that we are awaiting word regarding how Vina and Dino would would like their affiliation information to appear across the documents in C381, as well as Vina’s approval. Once these are received, we will move this document forward in the publication process. 
    >> 
    >> Best regards,
    >> RFC Editor/ap
    >> 
    >>>> On Sep 20, 2022, at 9:25 AM, Vrushali Ashtaputre (vrushali) <[e-mail]> wrote:
    >>> 
    >>> I approve.
    >>> 
    >>> Thank You,
    >>> Vrushali
    >>> 
    >>> -----Original Message-----
    >>> From: Alanna Paloma <[e-mail]>
    >>> Date: Tuesday, September 20, 2022 at 8:47 AM
    >>> To: Dino Farinacci <[e-mail]>
    >>> Cc: "Anton Smirnov (asmirnov)" <asmirnov=[e-mail]>, "Alberto Rodriguez-Natal (natal)" <[e-mail]>, "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>, "Vrushali Ashtaputre (vrushali)" <[e-mail]>, "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>
    >>> Subject: Re: [C381] AUTH48: RFC-to-be 9306 <draft-ietf-lisp-vendor-lcaf-12> for your review
    >>> 
    >>>  Hi Dino,
    >>> 
    >>>  Thank you for your reply. We have noted your approval on the AUTH48 status page:
    >>>    https://www.rfc-editor.org/auth48/rfc9306
    >>> 
    >>>  Best regards,
    >>>  RFC Editor/ap
    >>> 
    >>>> On Sep 19, 2022, at 12:37 PM, Dino Farinacci <[e-mail]> wrote:
    >>>> 
    >>>>> We will await approvals from Dino, Vina, and Vrushali prior to moving this document forward in the publication process.
    >>>> 
    >>>> I approve.
    >>>> 
    >>>> Dino
    >>>> 
    >>> 
    >>> 
    >> 
    >