SIP in higher education

[Stephen Kingham <>]

Hi

There is an interesting draft coming together on VoIP peering some of 
you may be interested in reviewing or at least being aware of.  You can 
find the draft 
here:http://www3.ietf.org/proceedings/05nov/agenda/voipeer.txt

And below is a part of a thread on the IETF voipeer (BOF).

Regards

Stephen Kingham

-------- Original Message --------
Subject:        [voipeer] Re: Comments on 
draft-meyer-voipeer-terminology-00.txt
Date:   Wed, 19 Oct 2005 15:14:13 -0700
From:   David Meyer 
<>
To:     Stastny Richard 
<>
CC:     
,
 

References:     
<>



On Wed, Oct 19, 2005 at 10:04:47PM +0200, Stastny Richard wrote:
> Hi all,
>  
> I am posting this on both the enum and the voipeer list, because there
> are some interdependencies in this draft.
>  
> ad Figure 1
>  
> I consider this figure very important and I suggest to draw a line above:
>  
> SIP URI <--- Call Routing Data (CRD)
>  
> This line indicates the scope boundary between ENUM WG and voipeer.

        Good point. I'll try to make that clear.

> The main task of ENUM is to deliver a SIP URI that
> can be used as Call Routing Data as defined in 3.1
>  
> How to deal with this call routing data is the task of voipeer.
>  
> Therefore I suggest to change the text below the figure from:
>  
> Note that voipeer is primarily concerned with the acquisition and use
>    of the Call Routing Data (CRD) shown in in Figure 1.  Importantly,
>    the CRD can be derived from an E.164 entry, as shown in Figure 1, or
>    via any other mechanism available to the user.
>  
> to
>  
> Note that ENUM is primarily concerned with the acquisition and 
>    voipeer primarily with the use
>    of the Call Routing Data (CRD) shown in in Figure 1.  Importantly,
>    the CRD can be derived from an E.164 entry in ENUM, as shown in Figure 1, 
> or
>    via any other mechanism available to the user.

        Sure. I think we had different meanings of "acquisition",
        but this is clear.

> ad 3.1.  Call Routing Data (CRD)
>    Call Routing Data, or CRD, is a SIP URI used to route a (real-time,
>    voice or other type) call to its termination point.
>    [ed: do we need a definition of "termination point"?]
>  
> yes and no:
>  
> I propose to change the text to:
> Call Routing Data, or CRD, is a SIP URI used to route a (real-time,
>    voice or other type) call to the destination network, where network
>    is defined in 3.4

        Sure.

>  
> ad 3.4.  Network
>    For purposes of this document and the voipeer work, a network is
>    defined to be the set of SIP servers and customers that are
>    controlled by a single administration. 
>  
> change to:
>    For purposes of this document and the voipeer and ENUM work, a 
>    network is
>    defined to be the set of SIP servers and end-users (customers)
>    that are controlled by a single administrative domain.
>    The network may also contain end-users on the PSTN.

        Yep.

> ad 3.6 Carrier (of Record)
>  
> The definition of a carrier is irrelevant for voipeer, voipeer
> is only dealing with L5 peering between VoIP Service providers
> as defined in 3.5 so either
>
> the definition is deleted or the definition of ENUM in
> draft-lind-infrastructure-enum-reqs-01 is used:
>  
> For purposes of this document, "Carrier of Record" refers to the
>    entity that provides PSTN service for an E.164 number with the
>    understanding that this definition is ultimately a matter for
>    national authorities to determine.

        Ok, no problem with that either.

> Proposal:
>  
> 4.1 User ENUM
>  
> In User ENUM the end-user having the right to use the
> E.164 number in question is responsible for the data
> entered in the corresponding domain within e164.arpa
> The end user hosted within a VoIP service providers network
> may enter CRD (a SIP URI) given to him by this VoIP 
> service provider.
>  
> Another VoIP service provider or end-user may query User ENUM 
> and use the retrieved CDR to route calls to the VoIP service
> providers network of the first user.
>  
> 4.2 Carrier ENUM
>  
> In carrier ENUM only Carrier of Records as defined in 3.6 
> (or ENUM) may enter data in the corresponding domain within tbd. 
> The Carrier of Record may enter may enter CRD (a SIP URI) 
> to allow other VoIP Service Providers to route calls to his network
> as defined within voipeer.
>  
> Note: ENUM may also contain other data beyond the CRD as defined
> in voipeer. This is out of scope for voipeer. This is especially true
> for data containing tel URIs. Tel URis are used to interconnect
> with the PSTN directly and are out of scope of voipeer. Endpoints
> on the PSTN served by a Carrier of Record and reachable via CDR
> and networks as defined in 3.4 are NOT out of scope.

	I'll fit this in too. 

        Thanks for the detailed comments,

        Dave



--
Stephen Kingham, MIT, BSc, E&C Cert
Project Manager and Consulting Engineer 
mailto:
Telephone +61 2 6222 3575 (office)
         +61 419 417 471 (mobile)
sip:

Voice and Video over IP
for The Australian Academic Research Network (AARNet)
http://www.aarnet.edu.au