RE: Draft-chiba-11 comments.

[Bernard Aboba <aboba@internaut.com>]

> The following are all candidates (NOTE: there maybe others that I missed).
>
> >    Request   Accept   Reject   Challenge   #    Attribute
> >    0-1       0-1      0        0            6   Service-Type
>
> Used to identify a service for which the COA applies.  It deosnt change the
> service-type but it MAY be used to categories CoA.

What happens if the Service-Type doesn't match? If this doesn't change the
service-type, then I'd say to omit it because it doesn't add value given
all the session identification attributes we already have.

> Don't know about the following either:
> >    0         0-1      0        0-1         71   ARAP-Features
> >    0         0-1      0        0           72   ARAP-Zone-Access
> >    0         0+       0        0           78   Configuration-Token
> >    0         0-1      0        0-1         84   ARAP-Challenge-Response

I don't think we can use attributes that are includable in a challenge.

> Don't know about these:
> >    0         0-1      0        0           88   Framed-Pool
> >    0         0+       0        0           99   Framed-IPv6-Route
> >    0         0-1      0        0          100   Framed-IPv6-Pool

Is Framed-Pool and Framed-IPv6-Pool used to *change* the IP address or to
identify the session?