Re: Review of draft-ietf-radext-vlan-02.txt

[Hannes Tschofenig <Hannes.Tschofenig@gmx.net>]

Hi Paul,

> > The question whether to provide the table only for a single 
> > port was resolved. Whether the table is actually user 
> > specific is another question. As such, the table would be 
> > indexed using the port number and the user "identity".
>
>
> The table, as defined by 802.1D, is a per-port table.  There is no
> facility within 802.1D to make this a per-user table.
Hmmm. This is then a bit surprising for me since RADIUS usage for the
User-Priority-Table attribute would then also be for user and not only 
for the port. An IEEE 802.1D implementation would have to store 1 
User-Priority-Table per port but with the mechanism proposed in your 
document (draft-ietf-radext-vlan-02.txt) there has to be 
N*User-Priority-Tables for a particular port, whereby N is the number of 
users attached to a particular port.

Do I miss something here?

Ciao
Hannes

>


--
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/>