Re: TLS requirements (Last Call: draft-ietf-atompub-protocol to Proposed Standard)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Robert,

--On March 13, 2007 3:23:22 PM -0400 Robert Sayre <rsayre@xxxxxxxxxxx> wrote:

This text is actively misleading, because it suggests RFC 4346 is
included for informational purposes. The text should read:

"At a minimum, client and server implementations MUST be capable of
 being configured to use HTTP Basic Authentication [RFC2617] in
 conjunction with a TLS connection as specified by [RFC2818] and
 [RFC4346]."

The text that got used in CalDAV (which is about to be published) is:

  o  MUST support transport over TLS [RFC2246] as defined in [RFC2818]
     (note that [RFC2246] has been obsoleted by [RFC4346]);

with 2246, 2818 and 4346 all normative references. These type of "up-references" are not ideal and I believe there was some discussion going on somewhere about how better to deal with this type of situation.

--
Cyrus Daboo


_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]