Re: [radext] Adoption call for draft-perez-radext-radius-fragmentation-06

[Alan DeKok <[e-mail]>]

Stefan Winter wrote:
> It doesn't know; it's an estimation which is hopefully rather accurate
> these days because many sane implementations of forwarding server do add
> Proxy-State; but they are not at all obliged to.

  From what I've seen, Proxy-State has little or no value.  FreeRADIUS
adds it because there's a suggestion to do so.  But it doesn't do
anything with Proxy-State.

> This begs the question: if a fragmentation-draft-unaware proxy receives
> a chunk close to 4096, and decides it wants to add an arbitrary
> attribute on its own, and cannot -> bad luck, discard?

  Pretty much.  Or, to *not* add the attribute.

> I also just found another gem regarding Proxy-State that I wasn't aware
> of until now: a forwarding server may truncate the Proxy-State values it
> found from earlier proxies, and only send its new one further on. It
> merely needs to remember the content of the earlier ones, to add them
> back in the reply. I'm speaking of this text in the same section:

  Yes.  I'm not aware of anyone who does that, though.

> The question of frag-unaware proxies remains; their only choice is to
> discard if they can't fit in their attributes.

  Yes.  That's a reason to either not re-write packets in a proxy, or to
keep the maximum packet size "small", to leave room for proxy re-writing.

  Alan DeKok.