Subject: RE: [Speermint] RE: [Enum] RE: [voipeer] I-D: Publishing SIP Peer ingPolicy

From: "Roy, Radhika R." <[email-masked]>
Date: Fri, 6 Jan 2006 13:19:20 -0500

Please see inline [RRR].

For example even within a domain

you may want a few sub-domains and these may well have very different

associated policies, and security and QoS expectations: 

[email-masked]

        - general flat-rate consumer voip service

[email-masked]

        - small-medium sized business voip, may involve IP-PBXs as

endpoints, whatever

[email-masked]

        - enterprise customers with higher QoS expectations

[email-masked]

        - free im & voip application service with best-efforts QoS

(meaning no QoS)

[RRR]  Domain name cannot be associated with any specific services per
URL/URI standards. It is true that a domain may have many sub-domains.

[RRR] Certain other mechanisms need to be found out to associate with
services, NOT directly in domain name URLs/URIs. 

_______________________________________________
enum mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/enum