Hi Michel,
Here is the command line we use:Python33\pythonpyang-1.4.1\bin\pyang 
D:\ietf-6top.yang

There is no error or warning come out.  Is it because of different compiler?
ThanksQin
 


     On Wednesday, June 10, 2015 4:57 AM, Michel Veillette 
<[email protected]> wrote:
   

 #yiv0196860943 #yiv0196860943 -- _filtered #yiv0196860943 
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv0196860943 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv0196860943 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv0196860943 
{font-family:Georgia;panose-1:2 4 5 2 5 4 5 2 3 3;}#yiv0196860943 
#yiv0196860943 p.yiv0196860943MsoNormal, #yiv0196860943 
li.yiv0196860943MsoNormal, #yiv0196860943 div.yiv0196860943MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv0196860943 h2 
{margin-right:0in;margin-left:0in;font-size:18.0pt;}#yiv0196860943 a:link, 
#yiv0196860943 span.yiv0196860943MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv0196860943 a:visited, #yiv0196860943 
span.yiv0196860943MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv0196860943 pre 
{margin:0in;margin-bottom:.0001pt;font-size:10.0pt;}#yiv0196860943 
span.yiv0196860943EmailStyle17 {color:#1F497D;}#yiv0196860943 
span.yiv0196860943Heading2Char {font-weight:bold;}#yiv0196860943 
span.yiv0196860943HTMLPreformattedChar {}#yiv0196860943 
.yiv0196860943MsoChpDefault {font-size:10.0pt;} _filtered #yiv0196860943 
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv0196860943 div.yiv0196860943WordSection1 
{}#yiv0196860943 Hi Qin    The file provided return some errors and warnings. 
Is it an issue with the file or the validation program? Validation results for 
ietf-6top.yang    *** Generated by yangdump-pro 14.08-6.2 *** Copyright (c) 
2008-2012, Andy Bierman, All Rights Reserved. *** Copyright (c) 2012-2015, 
YumaWorks, Inc., All Rights Reserved.    Error: Unexpected token 'greater than' 
in XPath expression '../EnforcePolicy <> DISABLE ./' ietf-6top.yang:256.36: 
error(245): wrong token type    Warning: top-level NP container 
'SecurityAttributes' is mandatory ietf-6top.yang:1025.7: warning(1048): 
top-level object is mandatory    *** 
/home/andy/swdev/ncorg/ncorg/ncorg/workdir/ietf-6top.yang *** 1 Errors, 1 
Warnings       
|   | Michel Veillette
System Architecture Director Trilliant Inc.
Tel: 450-375-0556 ext. 237
[email protected] www.trilliantinc.com     |

      From: Qin Wang [mailto:[email protected]]
Sent: 9 juin 2015 16:46
To: Michel Veillette; Michael Richardson; [email protected]
Subject: Re: [6tisch] 6top and neighbour list    Hi Michael and Michel,    The 
attached file is the Yang model, which has been embedded into 6top interface 
draft.    Thanks Qin       On Wednesday, June 10, 2015 4:23 AM, Michel 
Veillette <[email protected]> wrote:    Hi Michael

You will find in attachment the 6TiSCH YANG modules with a more consistent 
indentation and the missing headers for proper validation 
usinghttp://www.netconfcentral.com/run_yangdump. 

Michel Veillette
System Architecture Director
Trilliant Inc.
Tel: 450-375-0556 ext. 237
[email protected]
www.trilliantinc.com    
-----Original Message-----
From: 6tisch [mailto:[email protected]] On Behalf Of Michael Richardson
Sent: 9 juin 2015 13:18
To: [email protected]
Subject: [6tisch] 6top and neighbour list


1) I was reading draft-ietf-6tisch-6top-interface-03.
2) It seems that we have yet to adopt draft-wang-6tisch-6top-sublayer-01,
  it has expired, but draft-ietf-6tisch-6top-interface-03 still
  references that document.

I was looking for the description of the neighbour list that the PCE would need 
to know in order to construct the desired tracks.
(The indenting of the YANG model is very inconsistent; I could pull the XML off 
of bitbucket, and run it through an indenter if the authors wished)

I think that the information that I want about neighbours is:
  list NeighborList { ... }.

I think that if we have received an RPL DIO from that neighbour that we ought 
to show it's rank in that Neighborlist. I think that we ought to also indicate 
if that neighbour is *the* parent, and or if it is potential parent.

We might want to go further and say WHY the indicated parent was actually
chosen: but I think that this might be difficult to code in a vendor 
independant way.  I propose that we still do this, but allow the code to be 
vendor dependant.

--
Michael Richardson <[email protected]>, Sandelman Software Works  -= IPv6 
IoT consulting =-

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

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

Reply via email to