Re: [Netconf] FW: David Harrington's Discuss on draft-ietf-netconf-rfc4742bis-07: (withDISCUSS and COMMENT)

[Juergen Schoenwaelder <[e-mail]>]

On Thu, Mar 03, 2011 at 05:08:01PM +0100, Ersue, Mehmet (NSN - DE/Munich) wrote:
 
> Any comments? Pls also check the mail below from 
> David Harrington.

[... stuff removed I figured out is not helpful to send ...]

NETCONF is the wrong place to constraint user name. For SSH, this is
a no-brainer anyway.

/js

PS: We dealt with the uniquess questions explaining that this is an
    ACM issue and note that it is even mentioned in the Security
    Considerations section:

   [...] Second, it could be desirable to authorize based on
   mechanisms available in the secure transport layer (SSH, BEEP, etc).

PS: RFC 4252 says:

      byte      SSH_MSG_USERAUTH_REQUEST
      string    user name in ISO-10646 UTF-8 encoding [RFC3629]

    RFC 4251 says:

   string

      Arbitrary length binary string.  Strings are allowed to contain
      arbitrary binary data, including null characters and 8-bit
      characters.  They are stored as a uint32 containing its length
      (number of bytes that follow) and zero (= empty string) or more
      bytes that are the value of the string.  Terminating null
      characters are not used.

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
Fax:   [phone]         <http://www.jacobs-university.de/>