Andre,
Thanks
will fix and re-publish tom.
Abbie
-----Original Message-----
From: Andre Beck [mailto:abeck(_at_)bell-labs(_dot_)com]
Sent: Monday, April 05, 2004 5:20 PM
To: Barbir, Abbie [CAR:1A11:EXCH]
Cc: OPES Group
Subject: Re: FW: New authorization draft:
draft-ietf-opes-authorization-03
Abbie,
Looks good. Some nitpicks, mostly wrt to the uppercase keywords:
Section 3.3: "Implementation MUST not prohibit..."
"not" should be uppercase
Section 4.1: "The rule author, MAY not know specific service..."
delete comma; MAY should be lowercase
Section 4.1.3: "...modifications to the request MAY need..."
MAY should be lowercase
Section 4.2.3: "Some OPES services MAY need to be invoked..."
MAY should be lowercase
Section 4.3: "...with the architecture [ref ARCH] and this document."
should be a reference to [1]
Section 5.1.2: "...authorization databases MAY be easier..."
MAY should be lowercase
Section 5.1.3: "Authentication MAY be necessary..."
MAY should be lowercase
Section 5.5: "Tthe ability to prevent Traffic..."
should be "The"
-Andre
Abbie Barbir wrote:
-----Original Message-----
From: Barbir, Abbie [CAR:1A11:EXCH]
Sent: Friday, April 02, 2004 11:24 AM
To: Markus Hofmann; OPES Group
Cc: 'Marshall Rose'
Subject: New authorization draft: draft-ietf-opes-authorization-03
All,
Attached is the -03 of the authorization draft.
I have added a terminology and security sections + fixed
MUST etc.. .
Please review so we can re-submit to the IETF.
Abbie