Re: [dispatch] Fwd: New Version Notification for draft-procter-dispatch-outbound-discovery-00.txt

["Peterson, Jon" <[e-mail]>]

You're right that config profiles were supposed to be a potential way of
learning about outbound proxies, and RFC6080 does have some text about
finding a local profile. I'm not sure I'd call it a robust mechanism - it
basically assumes that DHCP or static configuration is giving you a local
domain name (like via RFC3361 or at worst RFC2132), and then you subscribe
to the config profile at that domain - but if you can bootstrap from that,
you could use it to get a config profile from the local administrative
domain.

But to your solidity point: did anyone ever specify a config profile for
actually configuring outbound proxies? Or for anything else, really?
RFC6080 is probably another solution to consider for this problem space,
but as far as I can recall there'd still be work to do there.

Jon Peterson
Neustar, Inc.

On 9/3/14, 1:24 PM, "Dale R. Worley" <[e-mail]> wrote:

>> From: "Peterson, Jon" <[e-mail]>
>
>> If solving for this were in scope, it would require a fairly generic
>> service discovery protocol. Like, for the network I am in, how do I
>> discover the necessary set of outbound proxy servers that will let
>> outbound traffic escape.
>
>This is getting close to what the "User Agent Profile Delivery" (RFC
>6080) was trying to do.  But that never reached solidity.
>
>> To the point of this thread, this is why this is all hand-wavy in
>>RFC5626,
>> if I recall correctly.
>
>IIRC, the UA profile delivery work was proceeding in parallel, which
>is why 5626 avoided discussing the topic.
>
>Dale