Re: [IPsec] I-D Action: draft-ietf-ipsecme-add-ike-07.txt

[Tero Kivinen <[e-mail]>]

[e-mail] writes:
> This version takes into account Tero's review, mainly:
> 
> * Indicate the encoding of the addresses
> * Split the ENCDNS_DIGEST_INFO figure into two
> * Add some text about CFG_ACK
> * clarify how the digest is computed
> * Add some examples
> 
> and some other minor edits. 

Can you add the other examples we had in our email exachange for
different requests, I think they provide useful information.

Also in examples it is useful to actually use names instead of
numbers, thats why I had (SHA2-256, SHA2-384, SHA2-512), and not (2,
3, 4). We are not using numbers for CP, CFG_REQUEST, or any other
fields...

Using only numbers would get really annoying:

   47(1) =
     8()
     10()
     TBA2()
     TBA3(0, (2, 3, 4))

:-)

And the ADN length field of the CFG_REPLY example is wrong, it says
16, but "doh.example.com" is only 15 characters long. Thats why my
example was using doh1.example.com :-)

I.e. it should be:

   CP(CFG_REPLY) =
     INTERNAL_IP6_ADDRESS(2001:db8:0:1:2:3:4:5/64)
     ENCDNS_IP6(1, 1, 15,
                   (2001:db8:99:88:77:66:55:44),
                   "doh.example.com",
                   (alpn=h2 dohpath=/dns-query{?dns}))
     ENCDNS_DIGEST_INFO(0, SHA2-256,
                           8b6e7a5971cc6bb0b4db5a71...)

-- 
[e-mail]