Subject: Re: [MEDIACTRL] Packages

From: "Eric Burger" <[email-masked]>
Date: Mon, 16 Apr 2007 08:31:21 -0700

Isn't a version number that really is just an opaque token that gets combined with another opaque token (the package name) more complex than just an opaque token?

That said, this reminds me exactly of the early H.248 package discussion...

--
Sent from my wireless e-mail device. Sorry if terse.  We all need lemonade: see <http://www.standardstrack.com/ietf/lemonade> for what lemonade is.

-----Original Message-----
From: Tim Melanchuk <[email-masked]>
To: Eric Burger
CC: Chris Boulton <[email-masked]>; [email-masked] <[email-masked]>
Sent: Mon Apr 16 08:01:22 2007
Subject: Re: [MEDIACTRL] Packages

we discussed this when we created the current set of packages.
i don't think we had stong reasons to do it either way and included
version numbers to be more explicit,  although the version numbers
work much like a new package. either a token identifying a 
package/version matches (and is supported) or it doesn't.

more sophisticated versioning requires additional mechanism.
i think we want to be careful about adding complexity here but
this is worth further discussion. 

timm

On 4/13/07, Eric Burger <[email-masked]> wrote:

	Would it be fair to say that packages do not version, and if you want to
	"upgrade" a package, you create a new package?
	
	-----Original Message-----
	From: Chris Boulton [mailto: [email-masked] <mailto:[email-masked]> ]
	Sent: Tuesday, April 10, 2007 5:07 AM
	To: Eric Burger; [email-masked]
	Subject: RE: [MEDIACTRL] Packages

	<chair-hat off>
	The whole package concept is pretty big.  Are we going to have, for 
	example, versioning?
	
	[Chris Boulton] There is already a simplistic versioning mechanism in
	the package drafts that is linked to the Control Package name that is
	registered.  E.g. 'msc-ivr-basic/1.0'. 
	
	  What happens if a requested version doesn't match?
	
	[Chris Boulton] At the moment you negotiate which packages you support
	based on the tokens (see the core framework).  If some don't match - we 
	have a SIP response that contains the one supported.
	
	  What if the
	requested version is "less than" the supported version?
	
	[Chris Boulton] Not covered at the moment - you either support or not 
	based on the token registered which include the version).  If we need to
	support a more sophisticated mechanism then it would be great to discuss
	the alternatives etc etc.
	
	Chris.

	
	Information contained in this e-mail and any attachments are intended 
	for the use of the addressee only, and may contain confidential
	information of Ubiquity Software Corporation. All unauthorized use,
	disclosure or distribution is strictly prohibited.  If you are not the
	addressee, please notify the sender immediately and destroy all copies 
	of this email. Ubiquity Software Corporation plc, a company registered
	under the laws of England and Wales, Registration 2719723, registered
	offices at Eastern Business Park, Building 3, Wern Fawr Lane, St.
	Mellons, Cardiff CF3 5EA, Wales, United Kingdom. 

	Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. 
	
	_______________________________________________
	MEDIACTRL mailing list
	[email-masked]
	https://www1.ietf.org/mailman/listinfo/mediactrl <https://www1.ietf.org/mailman/listinfo/mediactrl> 
	Supplemental Web Site:
	http://www.standardstrack.com/ietf/mediactrl

Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.

_______________________________________________
MEDIACTRL mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mediactrl
Supplemental Web Site:
http://www.standardstrack.com/ietf/mediactrl