headers
Internet-Drafts | 26 Aug 2004 21:34
Picon
Favicon

I-D ACTION:draft-ietf-rap-cops-tls-08.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Resource Allocation Protocol Working Group of the IETF.

	Title		: COPS Over TLS
	Author(s)	: J. Walker, A. Kulkarni
	Filename	: draft-ietf-rap-cops-tls-08.txt
	Pages		: 11
	Date		: 2004-8-26
	
This memo describes how to use TLS to secure COPS connections over 
the Internet.  
Please send comments on this document to the rap <at> ops.ietf.org 
mailing list.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rap-cops-tls-08.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-rap-cops-tls-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
(Continue reading)

Permalink | Reply | 0 comments |
headers
Wijnen, Bert (Bert | 31 Aug 2004 18:43
Picon
Favicon

AD review: draft-ietf-rap-cops-tls-08.txt submission

Here is what I found

1. Sect 4.1, it is unclear what kind of field the FLAGS field is
   is it a bitmask? an Unsigned16, or what? If a bit field, which
   bit indicates the TLS flag? I also wonder if the flag would not
   be better called StartTLS, but that is a nit.

2. Same sect 4,1
   Also, I guess the ///// field is a reserved field?
   If so, I would make that clear, and I would state that it 
   must be set to zero in transmit and be ignored on receipt.

3. I had this comment/question back inmarch of this year as well
   and have not yet seen a response:
     Section 7 states that the non-well-know port needs to be communicated
     by the server to the client. But it does not explain how. Am I missing
     something here?

4. You may want to add to the IANA considerations section that the registry
   is located at: http://www.iana.org/assignments/cops-parameters
   That is where they are supposed to add the error code.

5. Assigning value 16 as an error code is something that the WG should not
   do. The proper procedure is to mark it as a error-code-TBD-by-IANA
   and then ask IANA to assign and then RFC-Editor will fill in the numbers.
   I am not aware that other on-going work is taking place in this area,
   so the risk for conflicts is probably low.

6. I also still wonder:
   that StartTLS ClientSI object... who controls assignment of additional flags
(Continue reading)

Permalink | Reply | 0 comments |

Gmane