Hello,

draft-ietf-mif-dhcpv6-route-option-05 states in section 7.1:

   Metric field (available in previous version of this draft) has been
   replaced with 2-bit preference field that is in line with RIO
   information.

Issue1:

the section 4 states:


   In terms of the high level operation of the solution defined in this

   draft, a DHCPv6 client interested in obtaining routing information

   request the route options using the DHCPv6 Option Request Option

   (ORO) sent to a server.  A Server, when configured to do so, provides

   the requested route information as part of a nested options structure

   covering; the next-hop address; the destination prefix; >>the route

   metric<<; any additional options applicable to the destination or next-

   hop.

Given the statement in section 7.1, is "the route metric" above correct or is 
it an obsolete text?


Issue2:

section 5.2 states:
....


      0                   1                   2                   3

      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

     |       OPTION_RT_PREFIX        |          option-len           |

     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

     |                         Route lifetime                        |

     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

     | Prefix-Length |Resvd|Prf|Resvd|                               |

     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |

     |                            Prefix                             |

     |                          (up to 16 octets)                    |

     |                                                               |

     |                               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

     |                               |                               |

     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                               |

     .                                                               .

     .                         RT_PREFIX sub-options                 .

     .                                                               .

     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



                   Figure 3: Route Prefix Option Format


....


   Metric:   Route Metric. 8-bit signed integer.  The Route Metric

             indicates whether to prefer the next hop associated with

             this prefix over others, when multiple identical prefixes

             (for different next hops) have been received.
....


There is no "Metric" field shown in the Figure 3.

Thanks for clarification.

Kind regards


IVO SEDLACEK

Ericsson
Mobile +420 608 234 709
[email protected]
www.ericsson.com


[Description: Description: http://www.ericsson.com/]<http://www.ericsson.com/>

This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>

<<inline: image001.gif>>

<<inline: image002.gif>>

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

Reply via email to