Re: [TLS] Mentioning DTLS

On 3/15/2014 8:47 PM, Stephen Farrell wrote:
> So assuming nobody finds a problem with the erratum
> (and I remember;-) I'll mark it approved in a day or
> so.
>
> S

While this is a valid errata submission, reading 
https://www.ietf.org/iesg/statement/errata-processing.html - guideline 7 
suggests
that since this was present all the way back in 2006 and not fixed in 
this version, what the IESG is going to do is mark it as Hold for 
Document Update.   And we really should be implementing what's been 
written down, rather than writing down what's been implemented - at 
least for RFCs!

Mike

>
> On 03/14/2014 10:25 PM, Eric Rescorla wrote:
>> Martin R, thanks for pointing this out. Good catch.
>>
>> Martin T, thanks for the errata!
>>
>> -Ekr
>>
>>
>>
>> On Fri, Mar 14, 2014 at 3:11 PM, Martin Thomson <martin.thomson@gmail.com>wrote:
>>
>>> On 14 March 2014 14:10, Martin Thomson <martin.thomson@gmail.com> wrote:
>>>> On 14 March 2014 14:04, Martin Rex <mrex@sap.com> wrote:
>>>>> NEITHER of the two official DTLS specifications of the IETF does support
>>>>> TLS extensions.
>>>> I don't know how you came to that conclusion.  The definition of
>>>> ClientHello is inherited from the corresponding TLS specification,
>>>> isn't it?
>>> I see what the problem is now.  It looks like 6347 and co have opted
>>> to omit the extensions.  Most implementations I know of support
>>> extension, even though this was omitted.  Erratum on 6347 filed (4347
>>> is obsolete, so I'm not going to bother with it).
>>>
>>> http://www.rfc-editor.org/errata_search.php?rfc=6347&eid=3917
>>>
>>> _______________________________________________
>>> TLS mailing list
>>> TLS@ietf.org
>>> https://www.ietf.org/mailman/listinfo/tls
>>>
>>
>>
>> _______________________________________________
>> TLS mailing list
>> TLS@ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>
>