RE: Definition of the pres: URI in impp-pres-01

I agree, I don't see any motivation in our requirements (2778/2779) for a
single subscribe operation to target multiple discrete destinations. Doing
so would surely complicate our security model in a number of ways.

Jon Peterson
NeuStar, Inc.

> -----Original Message-----
> From: Jonathan Rosenberg [mailto:[email protected]]
> Sent: Friday, January 17, 2003 11:37 PM
> To: Derek Atkins
> Cc: Dave Crocker; Robert Sparks; [email protected]
> Subject: Re: Definition of the pres: URI in impp-pres-01
> 
> 
> I do not understand what the semantics of a SUBSCRIBE to such a thing 
> would mean. Does it mean that two separate subscriptions are 
> established, one to each address? Or, does it mean that there is some 
> server that acts as an aggregator; it will act as a client 
> and generate 
> subscribes to each of the two addresses, and I will have a single 
> subscription with that aggregator?
> 
> I don't recall much discussion on this point, and I think we 
> will find 
> there is a lot of complexity lurking here. Is there a good reason for 
> keeping the #? Can't we just make it a single mailbox?
> 
> -Jonathan R.
> 
> Derek Atkins wrote:
> > Dave Crocker <[email protected]> writes:
> > 
> > 
> >>Or do they, instead, want to permit:
> >>
> >>      pres:[email protected],pres:[email protected]
> > 
> > 
> > This is certainly what I envisioned, but I would like to 
> see more comments
> > from the the working group.
> > 
> > 
> >>In other words, we need to be very clear about the semantics of this
> >>URL.
> > 
> > 
> > -derek
> > 
> 
> -- 
> Jonathan D. Rosenberg, Ph.D.                72 Eagle Rock Ave.
> Chief Scientist                             First Floor
> dynamicsoft                                 East Hanover, NJ 07936
> [email protected]                     FAX:   (973) 952-5050
> http://www.jdrosen.net                      PHONE: (973) 952-5000
> http://www.dynamicsoft.com
> 
> 
> 
> 
> 
>   [reminder: [email protected] for non-technical 
> discussions, please]
> 
> 



  [reminder: [email protected] for non-technical discussions, please]