Re: [Fwd: Re: PEP draft for review]

Dan Connolly:
>
>Koen Holtman wrote:
>> Dan Connolly:
>> >Protocol-Info, on the other hand, is an entity header: it applies
>> >to resources, either those explicitly named using the "for" syntax,
>> Doesn't protocol-info apply to a single hop in the connection, not to the
>> resource on the origin server, when {scope conn} is used?
>
>Nope.
[...]
>There isn't any 'hop-only protocol info.'

Thanks, I think I understand now.  I thought that {scope conn} marked pep
extensions which are negotiated by two parties spanning a single hop in the
connection, while it actually marks extentions which require the
participation of every party along the connection.

>Dan

Koen.