Re: Fwd: New Version Notification for draft-troan-6man-universal-ra-option-03.txt

[Alexandre Petrescu <[e-mail]>]

I think why this will not be implemented in linux radvd is because of
the syntax of CDDL and CBOR being different than the radvd.conf syntax. 
I suspect the various dhcp daemon conf files would likely not understand
CDDL and CBOR either.  Probably conversions will be needed.

But I agree with the idea of the universal IPv6 configuration option to
be carried either by RA or by DHCP.

>   Fields:
> 
>    Type:  42 for Universal IPv6 Configuration Option
> 
>    Length:  The length of the option (including the type and length
>       fields) in units of 8 octets.
> 
>    Data:  CBOR encoded data.
> 
>    The Option is zero-padded to nearest 8-octet boundary.
> 
>    Example:
> 
>    {
>        "ietf":

That is an Example of just the Data field, I think.  The Example does
not seem to include Type and Length fields, which is ok.  It might be
sufficient to indent the word Example more to the right.

> The universal IPv6 Configuration option MUST be small enough to fit 
> within a single IPv6 ND or DHCPv6 packet.

I am not sure about this requirement... Idont know what is the size of a
single IPv6 ND packet, or of a DHCPv6 packet.

There is a field in the IP header containing the length of the packet in
(16bit, i.e. 65535 bytes max) but not in ND (ICMP) or DHCP headers.

There is a minimal MTU requirement but that is prior to fragmentation.
If fragmentation is in place then packets could be bigger.

Given that, I dont think one needs to compress data to fit in somewhere.

I agree that faced with sending human-readable ASCII data on an
otherwise low-level configuration protocol one might prefer to compress
that, as a principle of keeping human-readable data only at upper layers.

Alex


Le 07/10/2020 à 13:40, [e-mail] a écrit :
> I posted an update to the Universal Configuration option draft yesterday.
> Changes:
>    - removed the experimental part of it.
> 
> I think the draft is ready for working group adoption.
> Anyone else interested in this work?
> 
> (If the group decides to adopt it would be good with an additional 
> author, or an editor replacing me.
>  From a number of hats to juggle perspective.)
> 
> Written with indivudal contributor hat on,
> Ole
> 
> 
> 
>> Begin forwarded message:
>>
>> *From: *<[e-mail] <mailto:[e-mail]>>
>> *Subject: **New Version Notification for 
>> draft-troan-6man-universal-ra-option-03.txt*
>> *Date: *6 October 2020 at 22:21:59 CEST
>> *To: *"O. Troan" <[e-mail] <mailto:[e-mail]>>, Ole Troan 
>> <[e-mail] <mailto:[e-mail]>>
>>
>>
>> A new version of I-D, draft-troan-6man-universal-ra-option-03.txt
>> has been successfully submitted by O. Troan and posted to the
>> IETF repository.
>>
>> Name:draft-troan-6man-universal-ra-option
>> Revision:03
>> Title:The Universal IPv6 Configuration Option
>> Document date:2020-10-06
>> Group:Individual Submission
>> Pages:8
>> URL: 
>> https://www.ietf.org/id/draft-troan-6man-universal-ra-option-03.txt 
>> <https://www.ietf.org/id/draft-troan-6man-universal-ra-option-03.txt>
>> Status: 
>> https://datatracker.ietf.org/doc/draft-troan-6man-universal-ra-option/ 
>> <https://datatracker.ietf.org/doc/draft-troan-6man-universal-ra-option/>
>> Htmlized: 
>> https://datatracker.ietf.org/doc/html/draft-troan-6man-universal-ra-option 
>> <https://datatracker.ietf.org/doc/html/draft-troan-6man-universal-ra-option>
>> Htmlized: 
>> https://tools.ietf.org/html/draft-troan-6man-universal-ra-option-03 
>> <https://tools.ietf.org/html/draft-troan-6man-universal-ra-option-03>
>> Diff: 
>> https://www.ietf.org/rfcdiff?url2=draft-troan-6man-universal-ra-option-03 
>> <https://www.ietf.org/rfcdiff?url2=draft-troan-6man-universal-ra-option-03>
>>
>> Abstract:
>>   One of the original intentions for the IPv6 host configuration, was
>>   to configure the network-layer parameters only with IPv6 ND, and use
>>   service discovery for other configuration information.  Unfortunately
>>   that hasn't panned out quite as planned, and we are in a situation
>>   where all kinds of configuration options are added to RAs and DHCP.
>>   This document proposes a new universal option for RA and DHCP in a
>>   self-describing data format, with the list of elements maintained in
>>   an IANA registry, with greatly relaxed rules for registration.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of 
>> submission
>> until the htmlized version and diff are available at tools.ietf.org 
>> <http://tools.ietf.org>.
>>
>> The IETF Secretariat
>>
>>
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> [e-mail]
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>