Re: [IANA #1271464] expert review for draft-ietf-rtgwg-yang-rib-extend (xml-registry)

Acee Lindem <acee.ietf@gmail.com> Fri, 28 April 2023 12:37 UTC

Return-Path: <acee.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2BBC151985 for <rtgwg@ietfa.amsl.com>; Fri, 28 Apr 2023 05:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mj7LQxZvKDON for <rtgwg@ietfa.amsl.com>; Fri, 28 Apr 2023 05:37:31 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E79BC151527 for <rtgwg@ietf.org>; Fri, 28 Apr 2023 05:37:31 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id d75a77b69052e-3ef35d44612so98360171cf.1 for <rtgwg@ietf.org>; Fri, 28 Apr 2023 05:37:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682685450; x=1685277450; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=OHMgy7y7UB/MkoxTeKwm5ERq8CaH5fzg6JT0jjA/1aw=; b=iCjoTrYUoDUDmNBPDlSpbQYruk6h2u8JVG90B4van34LHAvnqbf3pYNIWM99OM8SsF voKhSbqmcXwyAZTYjHUt31v9ILfu3X3Bfz21HyxM27tnxt36RU3m77PsagDvVyFwrNhk CLOLNwmyH0LrBVpJGZo8jLCv2kv+9zaUyFKYlv1z5QbSx5uRbEvfpT1oy+QCOY2Mgvn6 tDZjUV/Rxz3krbRy0XSJLuX0sU/kHeVUBw+xJPo6WJr5w2dsHowbYtGdnVqSJkcuhlvA jfR31ydNUb8uajG51JdpWgFWxufoIIBPQMqTGKGMD0LcNpG729EocEkQjcoyB0sJhpfa YLHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682685450; x=1685277450; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=OHMgy7y7UB/MkoxTeKwm5ERq8CaH5fzg6JT0jjA/1aw=; b=MptOHGTurKSM0/8ryqfw+OauJPKkH7CwoP3B43fu/ERtGLPtNdsJMYVRUsCAjzBKjo I/P8R7GKIzjhM0nTGf7g5e7wvPbCSsvk5b9TR4DTWQ3bhXLVPl0YMTThJyEOmYqRFmzZ CdwkN/LvZN6WqIgCgjB8g7u3+Jb2clt8blH9A5208M0ncGkgsXMnSKM+1C2Xavy9IFiF pfSOdjE80NAnaLZua0s1WJVdSm4pTb0F20X0vFN5T70O7ZlsjX8fnEuR3CJnE22CPsnZ 4cCu4X29a1RfDNDNHE/VVmuB3cZveYwPesUd66X/laOyXXtHwRN5Shj35x/vhRVoo+xJ 0PFA==
X-Gm-Message-State: AC+VfDy0qhUU0Mk5E2XY5+JcaklonTkD6fK3DQ/76WO6saVpEBnGpXeh nWxS/aPDZ1XfbVH8ywJBJlA=
X-Google-Smtp-Source: ACHHUZ5KjRXzgXuBcHYtCW+TELMxNG64IIzoJgE2ZaFH3UYQH2F3S6EOqLWSLpBVUfuLMT+Bx3Gy+w==
X-Received: by 2002:a05:622a:346:b0:3ef:6bbb:aa56 with SMTP id r6-20020a05622a034600b003ef6bbbaa56mr8964415qtw.26.1682685450446; Fri, 28 Apr 2023 05:37:30 -0700 (PDT)
Received: from smtpclient.apple ([136.56.20.4]) by smtp.gmail.com with ESMTPSA id j14-20020ac84c8e000000b003ef3df76ec7sm6999186qtv.93.2023.04.28.05.37.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Apr 2023 05:37:29 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Subject: Re: [IANA #1271464] expert review for draft-ietf-rtgwg-yang-rib-extend (xml-registry)
From: Acee Lindem <acee.ietf@gmail.com>
In-Reply-To: <324824da-8190-4de6-ad94-08704cbe0fec@betaapp.fastmail.com>
Date: Fri, 28 Apr 2023 08:37:19 -0400
Cc: Yingzhen Qu <yingzhen.ietf@gmail.com>, Tim Bray <tbray@textuality.com>, Amanda Baber via RT <drafts-expert-review-comment@iana.org>, RTGWG <rtgwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <97BD423A-991D-47EF-8068-EF984C06CC3C@gmail.com>
References: <RT-Ticket-1271464@icann.org> <rt-5.0.3-1213521-1682543827-1210.1271464-9-0@icann.org> <rt-5.0.3-1213515-1682544198-1633.1271464-9-0@icann.org> <CAHBU6itPd43Di_t4_jAYfKBXev7cw+PUyicYJ4utWSrNUxMy4A@mail.gmail.com> <e62c7fd5-ca67-4248-a0e4-3999a37d8523@betaapp.fastmail.com> <35DBEB07-8942-4EA3-8057-16916D1DB592@gmail.com> <CABY-gOO3jpk2W3f50O5Kt+LpY1Tqw16KnfqbnPrO0DHDx8xkwA@mail.gmail.com> <324824da-8190-4de6-ad94-08704cbe0fec@betaapp.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/RwjqyPc_LFZwUbXt7WnyC2Azo-8>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2023 12:37:35 -0000

Hi Martin, 

Yingzhen updated with the -15 version last night. Please take a look. RFC 8792 is now an informative reference as well. Thanks for pointing out the need for the explanatory folding text. 

Thanks,
Acee

> On Apr 28, 2023, at 08:20, Martin Thomson <mt@lowentropy.net> wrote:
> 
> The registration is fine.  The rest of this mail is just nits.
> 
> My understanding is that you need to include that note *inside* the diagram/<artwork>/<sourcecode>.  Once for each diagram that includes it (you have two[*])
> 
> [*] But the JSON version doesn't need the line folding: a JSON parser will ignore whitespace so you can just wrap without the "\".
> 
> "The RFC text was produced using Marshall Rose's xml2rfc tool." is probably wrong.
> 
> On Fri, Apr 28, 2023, at 15:54, Yingzhen Qu wrote:
>> Hi Martin and Tim,
>> 
>> I submitted version -15 with reference to RFC 8792 and added the following text:
>> Note: '\' line wrapping per [RFC8792].
>> 
>> Please let us know if this resolves the issue.
>> 
>> Thanks,
>> Yingzhen
>> 
>> On Thu, Apr 27, 2023 at 6:31 PM Acee Lindem <acee.ietf@gmail.com> wrote:
>>> Hi Martin, 
>>> 
>>>> On Apr 27, 2023, at 00:07, Martin Thomson <mt@lowentropy.net> wrote:
>>>> 
>>>> This looks like a place where the document failed to include the standard RFC 8792 boilerplate.  Adding that would solve the problem, I think.
>>> 
>>> What do you mean by the “stardard RFC 8792 boilerplate”? What do you feel is missing from the draft. 
>>> 
>>> 
>>>> 
>>>> https://datatracker.ietf.org/doc/html/rfc8792#section-7.1.1
>>>> 
>>>> That is, the backslash will go away if you extract the content with the appropriate process.
>>>> 
>>>> Otherwise, those lines are really going to blow the 72 character limit.  Though perhaps the example would be cleaner if it used namespaces and moved the declarations to the top.  It's a bit repetitive as it is and maybe you don't need to invoke RFC 8792...
>>>> 
>>>>             <preference xmlns="urn:ietf:params:xml:ns:yang:\
>>>>               ietf-rib-extension">30</preference>
>>>>             <tag xmlns="urn:ietf:params:xml:ns:yang:\
>>>>               ietf-rib-extension">99</tag>
>>> 
>>> Right. We need to fold these longer lines. 
>>> 
>>> Thanks,
>>> Acee
>>> 
>>> 
>>>> 
>>>> 
>>>> On Thu, Apr 27, 2023, at 09:34, Tim Bray wrote:
>>>>> In the XML examples in Appendix B, we see things like this:
>>>>> 
>>>>>         <destination-prefix xmlns="urn:ietf:params:xml:ns:yang:\
>>>>>           ietf-ipv4-unicast-routing">0.0.0.0/0</destination-prefix>
>>>>> 
>>>>> Since the \-escaped newline is not legal in XML, the example would 
>>>>> cause failure if it were copy-and-pasted as is. So there should 
>>>>> probably be an editorial note clarifying that the \-escaped newlines 
>>>>> are there for clarity and should not be used in practice.  Or I guess 
>>>>> if you put in a perfectly legal newline before the xmlns= and again 
>>>>> before the ">", you might be able to avoid the escaping?
>>>>> 
>>>>> As with many other YANG namespaces, constructs such as 
>>>>> 
>>>>>     <address-family xmlns:v4ur="urn:ietf:params:xml:ns:yang:\
>>>>>       ietf-ipv4-unicast-routing">v4ur:ipv4-unicast</address-family>
>>>>> 
>>>>> are not interoperable in general-purpose XML tools, and it seems a 
>>>>> common practice in YANG-related RFCs neither to avoid this problem nor 
>>>>> to acknowledge its existence, so while I will continue to mention it 
>>>>> when I see it, I don't expect anyone to address it.
>>>>> 
>>>>> On Wed, Apr 26, 2023 at 2:23 PM David Dong via RT 
>>>>> <drafts-expert-review-comment@iana.org> wrote:
>>>>>> Dear Tim and Martin (cc: rtgwg WG),
>>>>>> 
>>>>>> As the designated experts for the ns registry, can you review the proposed registration in draft-ietf-rtgwg-yang-rib-extend for us? Please see
>>>>>> 
>>>>>> https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-rib-extend/
>>>>>> 
>>>>>> The due date is May 10, 2023.
>>>>>> 
>>>>>> If this is OK, when the IESG approves the document for publication, we'll make the registration at
>>>>>> 
>>>>>> https://www.iana.org/assignments/xml-registry/
>>>>>> 
>>>>>> With thanks,
>>>>>> 
>>>>>> David Dong
>>>>>> IANA Services Specialist
>>>> 
>>>> _______________________________________________
>>>> rtgwg mailing list
>>>> rtgwg@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/rtgwg
>>> 
>>> _______________________________________________
>>> rtgwg mailing list
>>> rtgwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtgwg