Re: [Last-Call] Artart last call review of draft-ietf-dnsop-dns-tcp-requirements-12

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Warren,

> On Sep 11, 2021, at 6:20 PM, Warren Kumari <warren@xxxxxxxxxx> wrote:
> 
> 
> 
> On Sat, Sep 11, 2021 at 4:09 PM Robert Sparks <rjsparks@xxxxxxxxxxx> wrote:
> 
> 
> On 9/11/21 11:03 AM, Bob Hinden wrote:
>> Hi Warren,
>> 
>> 
>>> On Sep 10, 2021, at 4:19 PM, Warren Kumari <warren@xxxxxxxxxx>
>>>  wrote:
>>> 
>>> 
>>>> Seems reasonable to consider, assuming a BCP can update an Informational RFC?
>>>> 
>>> Any RFC can update any previous RFC?  There are some questions about the
>>> use of "Updates" (see draft-kuehlewind-update-tag); different WGs use it
>>> for different things. If you are trying to catch the eye of
>>> implementers, maybe it would help, but perhaps ask your AD.
>>> 
>>> Yup, it should be able to.
>>> W
>>> 
>> Are you sure?
>> 
>> For example, can an “Experimental" RFC update an RFC at “Standard”?    Can an RFC from one Stream update an RFC in another Stream?   Lots of other cases come to mind.
>> 
>> This seems a lot more subtle than any RFC can update any other RFC.
>> 
>> Bob
>> 
> I think Warren was answering the question about this particular potential BCP updating a particular Informational RFC both in the IETF stream.
> 
> 
> Yup, what Robert said…

Fair enough, but good to clarify.

Bob


Attachment: signature.asc
Description: Message signed with OpenPGP

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux