RPSLng info please

[Dimitrios Kalogeras <]

 I would like to have your opinion on the following issues.

I beleive the last draft
http://www.ietf.org/internet-drafts/draft-blunk-rpslng-03.txt
has some serious typos.

Specifically in section 2.5  the definition of EXCEPT and REFINE do not
allow for nay curly bracket after the EXCEPT or REFINE .

mp-import ::=
          [protocol <protocol-1>] [into <protocol-2>] <import-expression>

   <import-expression> ::=
          [afi <afi-list>] <import-term> accept <mp-filter> |
          [afi <afi-list>] <import-term> accept <mp-filter> EXCEPT
                                                 <import-expression> |
          [afi <afi-list>] <import-term> accept <mp-filter> REFINE
                                                 <import-expression>

   <import-term> ::=  <import-factor> |
                      {
                        <import-factor>
                        ...
                        <import-factor>
                      }

   <import-factor> ::= from <mp-peering> [action <action>];

While in the policy examples there are curly brackets after REFINE and
EXCEPT.

The second issue is with regard of the logic of REFINE and EXCEPT
statements.

Does the RPSLng REFINE statements refines the afi protocol list ?
if yes then this is not shown in the grammar.

Assume for example that I would like to express a policy like

import from  AS-ANY accept ANY
   but from  AS 1  if accept community (1:3);(action xxx);
   but from  AS 1  if accept community (1:5); action yyy);

how  do I express this  in RPSL ng? Is this a typical usage of REFINE or
EXCEPT statement ?

If this is a typiical usage of EXCEPT statement it would be nice to have
some kind of appendinx for porting policies from rfc2622 to RPSLng.

Regards,
Dimitrios
--
--

Dimitrios K. Kalogeras

Electrical Engineer Ph.D.
Network Manager
NTUA/GR-Net Network Management Center
_____________________________________
icq:   11887484
voice: +30-210-772 1863
fax:     +30-210-772 1866
e-mail: D.Kalogeras@localhost
pub  1024D/F2A69A72 2002-12-13 Dimitrios Kalogeras <D.Kalogeras@localhost
     Key fingerprint = 64C5 646D 8D33 A3FF 14D1  66C6 5127 54CC F2A6 9A72