Subject: RE: [SIP] draft-petrie-sip-config-framework-00.txt

From: "Rosen, Brian" <[email-masked]>
Date: Thu, 8 Mar 2001 17:07:43 -0500

One of the more unpleasant tasks a WG chair gets to do is tell
someone that we aren't going to solve his favorite problem.
This is one of those times.  In consultation with my co-chairs,
we are going to rule this discussion out of scope, at least for
now.

You will see such messages with distressing regularity now, but the
workload is such that we have to say "no" more often.

You are of course free to pursue this outside of the sip WG,
including submission of an RFC to the IESG.

Brian

> -----Original Message-----
> From: Daniel G. Petrie [mailto:[email-masked]]
> Sent: Friday, March 02, 2001 6:13 PM
> To: IETF SIP (E-mail); [email-masked]
> Subject: [SIP] draft-petrie-sip-config-framework-00.txt
> 
> 
> This draft proposes a configuration and management framework
> 
> for SIP user agents. It has been submitted and is in the
> pipeline.
> You can access this in the mean time from:
> http://www.pingtel.com/docs/draft-petrie-sip-config-framework-00.txt
> 
> Abstract
> 
>    This document defines the application of a set of
> protocols for
>    configuring a SIP user agent.  The SIP user agent must
> discover how
>    and from where to retrieve its initial configuration and
> be notified
>    of changes and updates which impact its configuration.
> The
>    objective is to define a means for automatically
> configuring a user
>    agent such that it can be functional without user or
> administrative
>    intervention.  The framework for discovery, delivery,
> notification
>    and updates of user agent configuration is defined here.
> This
>    framework is also intended to ease ongoing
> administration,
>    configuration and upgrading of large scale deployments of
> SIP user
>    agents.  The contents and format of the configuration
> data to be
>    defined is outside the scope of this document.
> 
> 
> 
> _______________________________________________
> This list is for continuing development of the SIP protocol.
> The sip-implementor's list is the place to discuss implementation,
> and to receive advice on understanding existing sip.
> To subscribe to it, send mail to 
> [email-masked] with "subscribe" in the body.
> 

_______________________________________________
This list is for continuing development of the SIP protocol.
The sip-implementor's list is the place to discuss implementation,
and to receive advice on understanding existing sip.
To subscribe to it, send mail to 
[email-masked] with "subscribe" in the body.