Hi Tero,

  Groups 1 and 2 were defined in RFC 2409 and repeating them in a
subsequent RFC does not change that. I suggest leaving the reference
to RFC 2409 for groups 1 and 2 (and 3 and 4 for that matter) that
currently exists today at http://www.iana.org/assignments/ipsec-registry,
as of 2315 GMT on 30 November 2009, aka "right now".

  regards,

  Dan.

On Mon, November 30, 2009 4:43 am, Tero Kivinen wrote:
> Now talking only about the Tranform Type 4 - Diffie-Hellman Group
> Transform IDs IANA registry.
>
> Valery Smyslov writes:
>> Currently exact groups for numbers 1, 2, 14, 15, 16, 17 and 16 are not
>> defined in IANA.
>> For me this is inconsistent. Either change two abovementioned lines to:
>>
>> 1             768-Bit MODP Group                    [RFC4306]
>> 2             1024-Bit MODP Group                  [RFC4306]
>>
>> 14           2048-Bit MODP Group                  [RFC3526]
>> 15           3072-Bit MODP Group                  [RFC3526]
>> 16           4096-Bit MODP Group                  [RFC3526]
>> 17           6144-Bit MODP Group                  [RFC3526]
>> 18           8192-Bit MODP Group                  [RFC3526]
>
> Hmm... I think the IANA registry should really list these out, instead
> of using range to reference to the RFCs.
>
> I think we should fix the IANA registry so the group names will match
> the section / appendix names in the appropriate RFCs and where there
> would not be any range allocations. The resulting IANA registry would
> be like this:
> ----------------------------------------------------------------------
> Registry Name: Transform Type 4 - Diffie-Hellman Group Transform IDs
> Reference: [RFC4306]
> Registration Procedures: Expert Review
>
> Registry:
> Number        Name                                Reference
> ------------  ----------------------------------  ---------
> 0             NONE                                [RFC4306]
> 1             Group 1 - 768 Bit MODP Group        [RFC4306]
> 2             Group 2 - 1024 Bit MODP Group       [RFC4306]
> 3-4           Reserved                            [RFC4306]
> 5             1536-bit MODP Group                 [RFC3526]
> 6-13          Unassigned                          [RFC4306]
> 14            2048-bit MODP Group                 [RFC3526]
> 15            3072-bit MODP Group                 [RFC3526]
> 16            4096-bit MODP Group                 [RFC3526]
> 17            6144-bit MODP Group                 [RFC3526]
> 18            8192-bit MODP Group                 [RFC3526]
> 19            256-bit random ECP group            [RFC4753]
> 20            384-bit random ECP group            [RFC4753]
> 21            521-bit random ECP group            [RFC4753]
> 22            1024-bit MODP Group with 160-bit    [RFC5114]
>               Prime Order Subgroup
> 23            2048-bit MODP Group with 224-bit    [RFC5114]
>               Prime Order Subgroup
> 24            2048-bit MODP Group with 256-bit    [RFC5114]
>               Prime Order Subgroup
> 25            192-bit Random ECP Group            [RFC5114]
> 26            224-bit Random ECP Group            [RFC5114]
> 27-1023       Unassigned                          [RFC4306]
> 1024-65535    Private use                         [RFC4306]
> ----------------------------------------------------------------------
>
> Unless anybody objects, I will be requesting IANA to make the change
> next week.
>
> --
> kivi...@iki.fi
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>


_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to