RE: Redirection Draft v1 is now available for review

[Avi Lior <avi@bridgewatersystems.com>]

I agree.  I basically stole these definition or this style from Diameter see
RFC3588

We could do a better job but I was hoping that if they got away with it so
could we.  But perhaps not.

Lets see what others say.

> -----Original Message-----
> From: Ignacio Goyret [mailto:igoyret@lucent.com] 
> Sent: Tuesday, July 20, 2004 7:38 PM
> To: Avi Lior
> Cc: radiusext@ops.ietf.org
> Subject: Re: Redirection Draft v1 is now available for review
> 
> 
> At 21:35 7/20/2004 -0400, Avi Lior wrote:
> >
> >Subject: I-D ACTION:draft-lior-radius-redirection-01.txt
> 
> Avi,
> The format to be used for NAS-Filter-Rule at the top of page 
> 13 is not very clear to me from reading this doc. In 
> particular, it is not clear to me:
> - whether the words 'from' and 'to' should or should not be used
> - if the '/' character in the port spec is a character to be inserted
>   or it means alternate choices (as in 'port' or 'port-port').
> - is the '!' character allowed before port specs (to indicate
>   "everything except these ports").
> - are the "from" and "to" parts always required? Is either 
> one optional?
>   If so, is the other mandatory? (eg, if the "to" part is optional,
>   is the "from" part mandatory?)
> - which words are keywords that must be entered as is and which ones
>   are tokens.
> - for "ipoptions": is the comma-separated list an AND-condition (where
>   all the listed options must be present) or an OR-condition 
> (where any
>   of the listed options must be present). Same for "tcpoptions" and
>   "tcpflags".
> 
> Similar questions rise from reading the other rules 
> (IP-Redirection-Rule and HTTP-Redirection-Rule).
> 
> Please consider clarifying them. Examples are not necessarily 
> needed but can definitely help convey the idea.
> 
> Best regards,
> -Ignacio
> 

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>