Tom,
Please see one additional clarification inline.
Cheers,
Med
> -----Message d'origine-----
> De : tom petch <daedulus@xxxxxxxxxxxxx>
> Envoyé : mercredi 18 mai 2022 10:40
> À : last-call@xxxxxxxx
> Cc : adrian@xxxxxxxxxxxx; opsawg@xxxxxxxx; opsawg-chairs@xxxxxxxx;
> draft-ietf-opsawg-l2nm@xxxxxxxx
> Objet : Re: Last Call: <draft-ietf-opsawg-l2nm-15.txt> (A YANG
> Network Data Model for Layer 2 VPNs) to Proposed Standard
>
> On 29/04/2022 15:40, The IESG wrote:
> > The IESG has received a request from the Operations and
> Management Area > Working Group WG (opsawg) to consider the
> following document: - 'A YANG > Network Data Model for Layer 2
> VPNs'
> > <draft-ietf-opsawg-l2nm-15.txt> as Proposed Standard
>
...
> s.7.5.2 has
> +--rw (signaling-option)? choice
> | +--:(bgp) case
> | | ... choice bgp-type
> | +--:(ldp-or-l2tp) case
>
> so I expect to see
> choice signaling-option which I do on page 87
> case bgp also on page 87
> ....
> case ldp-or-l2tp nowhere to be seen.
> In fact, there is no case, rather there is a container with that
> identifier on page 93. This is valid YANG - a container can
> stand in
> for a case - but with six pages of YANG in-between, this is hard
> to
> follow. I would suggest /container/case/ or if there is a reason
> for
> not using case, then add a comment to that effect in the YANG
> module
> prior to the container statement.
>
[Med] I prefer to maintain the current structure as it adheres with this part from 7950
As a shorthand, the "case" statement can be omitted if the branch
contains a single "anydata", "anyxml", "choice", "container", "leaf",
"list", or "leaf-list" statement. In this case, the case node still
exists in the schema tree, and its identifier is the same as the
identifier of the child node.
I made this change to remind this is still part of the choice:
OLD:
container ldp-or-l2tp {
description
"Container for LDP or L2TP-signaled PWs. ";
NEW:
container ldp-or-l2tp {
description
"Container for LDP or L2TP-signaled PWs
choice.";
> Tom Petch
_________________________________________________________________________________________________________________________
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.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
