Re: [Speermint] Basic Peering Requirements

Pfautz, Penn L, GBLAM wrote:
> I wouldn't count on routing data necessarily being public even if TNs
> are.  

Publishing a phone number in ENUM does not imply that routing 
information/ingress point is public.

This is what Otmar's domainpolicy and federation drafts describes, and 
what is already implemented in the openser domainpolicy module:

A short description:

1. ENUM entry for +43 123
3.2.1.3.4 NAPTR 100 10 "u" "e2u+SiP" "!^.*$!sip:123@mydom.foo!" .

This reveals an identifier to mydom.foo.

2. Now, as defined in draft-lendl-domain-policy-ddds find out the 
peering policy of mydom.foo by looking up NAPTRs of mydom.foo.

mydom.foo. NAPTR 10 50 ("U" "D2P+SIP:fed"
       "!^.*$!http://xyconnect.foo/!" . )
mydom.foo. NAPTR 20 50 ("U" "D2P+SIP:fed"
       "!^.*$!http://crossconnect.foo/!" . )

In this example mydom can be contacted via the xyconnect.foo federation 
and the crossonnect.foo federation. The final step - how to come from 
the URI sip:123@mydom.foo to the ingress point (IP address, port, 
transport protocol) - is a matter of the federation policy. This may be 
public or private - a federation policy.

Thus, ENUM does not imply that routing data is public.

-- 
Klaus Darilion
nic.at

_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www1.ietf.org/mailman/listinfo/speermint