Nitin,
In section 2.3 it says:
" A route is essentially a match condition and an action following the
   match.  The match condition specifies the kind of route (IPv4, MPLS,
   etc.) and the set of fields to match on.  Figure 3 represents the
   overall contents of a route ... This document specifies the following match 
types:

   o  IPv4: Match on destination IP address in the IPv4 header

   o  IPv6: Match on destination IP address in the IPv6 header 
...
  o  IP multicast: Match on (S, G) or (*, G), where S and G are IP
      prefixes"


However, section 6 defines:
"<match> ::= <route-type> (<ipv4-route> | <ipv6-route> | <mpls-route> |
                            <mac-route> | <interface-route>)
  <route-type> ::= <IPV4> | <IPV6> | <MPLS> | <IEEE_MAC> | <INTERFACE>

  <ipv4-route> ::= <ip-route-type>
                   (<destination-ipv4-address> | <source-ipv4-address> |
                    (<destination-ipv4-address> <source-ipv4-address>)) ...

  <ipv6-route> ::= <ip-route-type>
                   (<destination-ipv6-address> | <source-ipv6-address> |
                    (<destination-ipv6-address> <source-ipv6-address>))
"
The terms using source address are probably meant for multicast, if this is the 
intention it should be changed to match the definition:
(S, G) or (*, G).

Thanks,
Yael 



On 5/27/14, 2:38 PM, [email protected] wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>   This draft is a work item of the Interface to the Routing System Working 
> Group of the IETF.
>
>          Title           : Routing Information Base Info Model
>          Authors         : Nitin Bahadur
>                            Ron Folkes
>                            Sriganesh Kini
>                            Jan Medved
>       Filename        : draft-ietf-i2rs-rib-info-model-03.txt
>       Pages           : 24
>       Date            : 2014-05-27

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

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

Reply via email to