Hi, I am a little concerned by text that specifies mandatory or optional features without using the RFC2119 keywords. I would prefer tighter text that uses the RFC2119 keywords, throughout the document.
Text like "is allowed" does not give clear enough directions to implementers of receivers versus senders; we need to be clear what "conservative what you send" means. dbh > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Martin Schütte > Sent: Thursday, August 28, 2008 1:04 AM > To: [email protected] > Subject: Re: [Syslog] Need your input on final issueson > draft-ietf-syslog-transport-tls > > Chris Lonvick schrieb: > > have comments, please send them in. If you read these and > agree with the > > changes, please comment to the WG list as well so we know > that we're > > getting an adequate review. > > Looks good to me. Only one question: > > > === 1 === > > The '*' (ASCII 42) wildcard character is allowed in > subjectAltName > > values of type dNSName (and in Common Name, if used), > and then only > > as the left-most (least significant) DNS label in that > value. This > > Is this a MAY or a MUST? > > > -- > Martin > _______________________________________________ > Syslog mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/syslog > _______________________________________________ Syslog mailing list [email protected] https://www.ietf.org/mailman/listinfo/syslog
