Re: [mif] Advancement of draft-ietf-mif-dhcpv6-route-option?

[Ivo Sedlacek <[e-mail]>]

Hello,

can you please also correct the errors identified in the attached mail?

Kind regards

Ivo Sedlacek 

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


-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Alexandru Petrescu
Sent: 3. února 2013 19:54
To: mif
Subject: [mif] Advancement of draft-ietf-mif-dhcpv6-route-option?

Hello,

I wonder what is the advancement direction about of draft-ietf-mif-dhcpv6-route-option.

I remember an advantageous voting procedure in Atlanta, and I hoped to see confirmation on the email list if necessary.

That voting and its confirmation could help close many of the raised issues, right?

Tickets are at:
http://trac.tools.ietf.org/wg/mif/trac/report/1

Regards,

Alex
_______________________________________________
mif mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mif

--- Begin Message ---

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



Description: Description: line

IVO SEDLACEK


Ericsson
Mobile [phone]
[e-mail]
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>

--- End Message ---