Tom, Lada, Stephane, 
I've changed the XML formatting so that the actual ietf-isis.yang model can be 
embedded as is without any substitution characters. This is in the -33 version. 
There are no other changes in this version (other than removing some trailing 
white spaces and expanding tabs). 
Thanks,
Acee 

On 1/23/19, 4:09 AM, "Ladislav Lhotka" <[email protected]> wrote:

    Hi Stéphane,
    
    the problem is in the source of the "ietf-isis" module inside <artwork>: the
    chevrons enclosing email addresses should be encoded as XML entities &lt; 
and
    &gt; but what I see there is &amp;lt; and &amp;gt;
    
    Lada
    
    On Tue, 2019-01-22 at 16:18 +0000, [email protected] wrote:
    > Hi Tom,
    > 
    > This is plaintext. You can see it in the XML source of the draft, there 
is no
    > link in the YANG module.
    > Is your concern coming from the "[" "]" characters ? Just a copy/paste 
from
    > the text version of the boilerplate, but there is no link behind.
    > 
    > 
    > -----Original Message-----
    > From: Lsr [mailto:[email protected]] On Behalf Of tom petch
    > Sent: Tuesday, January 22, 2019 13:48
    > To: Acee Lindem (acee); Yingzhen Qu; [email protected]; 
    > [email protected]
    > Subject: Re: [Lsr] Shepherd review comments on 
draft-ietf-isis-yang-isis-cfg-
    > 29
    > 
    > -32 has the RFC2119 boilerplate in the YANG module - thank you - but...
    > YANG modules must be plain text and
    > 
    >          "are to be interpreted as described in BCP 14 [RFC2119]
    >           [RFC8174] when, and only when, they appear in all capitals, as
    >           shown here."
    > 
    > looks rather like XML/HTML anchors and not plain text.
    > 
    > Time idnits learnt what a YANG module looks like!
    > 
    > Tom Petch
    > 
    > ----- Original Message -----
    > From: "Acee Lindem (acee)" <[email protected]>
    > To: "Yingzhen Qu" <[email protected]>; <[email protected]>;
    > <[email protected]>
    > Sent: Monday, January 21, 2019 9:07 PM
    > Subject: Re: [Lsr] Shepherd review comments on
    > draft-ietf-isis-yang-isis-cfg-29
    > 
    > 
    > > Hi Yingzhen,
    > > All the idnits warnings are fixed in the -32 version of the drafts.
    > > Thanks,
    > > Acee
    > > 
    > > From: Yingzhen Qu <[email protected]>
    > > Date: Friday, January 18, 2019 at 5:35 PM
    > > To: "[email protected]" <[email protected]>,
    > "[email protected]"
    > <[email protected]>
    > > Subject: Shepherd review comments on draft-ietf-isis-yang-isis-cfg-29
    > > Resent-From: <[email protected]>
    > > Resent-To: Stephane Litkowski <[email protected]>, Derek
    > Yeung <[email protected]>, Acee Lindem <[email protected]>, Jeffrey Zhang
    > <zzhang@juniper.
    > 
    > _______________________________________________
    > Lsr mailing list
    > [email protected]
    > https://www.ietf.org/mailman/listinfo/lsr
    > 
    > 
______________________________________________________________________________
    > ___________________________________________
    > 
    > Ce message et ses pieces jointes peuvent contenir des informations
    > confidentielles ou privilegiees et ne doivent donc
    > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez 
recu ce
    > message par erreur, veuillez le signaler
    > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
    > electroniques etant susceptibles d'alteration,
    > Orange decline toute responsabilite si ce message a ete altere, deforme ou
    > falsifie. Merci.
    > 
    > This message and its attachments may contain confidential or privileged
    > information that may be protected by law;
    > they should not be distributed, used or copied without authorisation.
    > If you have received this email in error, please notify the sender and 
delete
    > this message and its attachments.
    > As emails may be altered, Orange is not liable for messages that have been
    > modified, changed or falsified.
    > Thank you.
    > 
    -- 
    Ladislav Lhotka
    Head, CZ.NIC Labs
    PGP Key ID: 0xB8F92B08A9F76C67
    
    

_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr

Reply via email to