Hi Med,

That's very good that you are NMDA compliant.

I didn't pay much attention and thought that both ietf-dslite-aftr@2017-08-10 and ietf-...@2017-07-03.yang were part of draft-ietf-softwire-dslite-yang-05.txt Actually ietf-...@2017-07-03.yang comes from https://datatracker.ietf.org/doc/draft-sivakumar-yang-nat/ Since ietf-dslite-aftr@2017-08-10 imports ietf-...@2017-07-03.yang, the next step is to modify ietf-...@2017-07-03.yang to be NMDA compliant, right?

Also, how can draft-ietf-softwire-dslite-yang progress without progressing this normative reference?

   8.1. Normative references

                  Sivakumar, S., Boucadair, M., and S. Vinapamula, "YANG
                  Data Model for Network Address Translation (NAT)", draft-
                  sivakumar-yang-nat-07 (work in progress), July 2017.

Regards, Benoit
Hi Benoit,

Please see inline.


-----Message d'origine-----
De : Benoit Claise [mailto:bcla...@cisco.com]
Envoyé : vendredi 11 août 2017 11:01
À : draft-ietf-softwire-dslite-y...@ietf.org; softwires@ietf.org
Objet : YANG validation issue with draft-ietf-softwire-dslite-yang-05.txt

Dear authors,

I see that you posted a new version, but there are still some errors
See http://www.claise.be/IETFYANGPageCompilation.html
See https://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-yang/ =>
YANG validation

augment "/nat:nat-module/nat:nat-instances/nat:nat-instance" {

NEW: I guess this should be
augment "/nat:nat-config/nat:nat-instances/nat:nat-instance" {

[Med] Actually, the OLD one is correct. We changed the NAT module to be aligned 
with the NDMA recommendation (so, we don't have any more nat-config)


NEW: I guess this should be

[Med] Idem as above. We don't have anymore a nat-state in the new NAT module.

Attached is the updated YANG module that validates.

[Med] Thank you.

Regards, Benoit

Softwires mailing list

Reply via email to