- enum-wg - mailman.ripe.net

Forward DOMAIN Object Cleanup and Syntax Changes
by Denis Walker 31 Jan '12

31 Jan '12

[Apologies for duplicate emails] Dear colleagues, At RIPE 57, the RIPE NCC was asked to remove all forward domain data from the RIPE Database. The last two ccTLD operators' data was removed today, 31 January 2011. The RIPE NCC can now confirm the completion of action point AP57.2 from the RIPE Database Working Group. At RIPE 62, the RIPE NCC was asked to look at the attributes in DOMAIN objects. With the removal of any hierarchy in reverse delegations and the removal of forward domain data, we no longer see any use case for the "mnt-lower:" attribute. Other attributes that it has been suggested were used only for forward domains are: - "refer:" - "sub-dom:" - "dom-net:" The statistics listed at the bottom of this email show how many of these attributes have been added to ENUM and reverse delegation DOMAIN objects. It has also been suggested that the "nserver:" optional attribute could be made a "required" attribute in reverse delegation DOMAIN objects. It could remain optional in ENUM DOMAIN objects or it could be disallowed. The RIPE NCC asked the community in July 2011 if anyone saw any justification for the use of these attributes in ENUM or reverse delegation DOMAIN objects. We did not receive any feedback on this. If there is no justification, the syntax of the DOMAIN object can be adjusted to deprecate these attributes. Then all current DOMAIN objects in the RIPE Database can be "cleaned" to remove this data. Business rules can be added to make the "nserver:" attribute required or disallowed in different types of DOMAIN objects, if this is considered useful. To keep the discussion focused, please send any comments or feedback to the DNS Working Group mailing list. Regards, Denis Walker Business Analyst RIPE NCC Database Group Statistics (as at July 2011) ---------- Number of each attribute used in reverse delegations or ENUMs and the number of unique maintainers who manage these objects. "refer:" = 6 unique maintainers = 1 "sub-dom:" = 271 unique maintainers = 23 "dom-net:" = 2,219 unique maintainers = 140 "mnt-lower:" = 46,485 unique maintainers = 4,208

1 0

Infrastructure ENUM developments in Germany/.de/+49
by Carsten Schiefner 25 Jan '12

25 Jan '12

Dear colleagues, first of all, on behalf of the ENUM WG Co-Chairs I wish you all a Happy New 2012! ENUM-wise, it didn't start too bad: we have already been able to see the announcement of XConnect and DE-CIX wrt. an NGN/VoIP communications exchange where one core component is ENUM: http://www.xconnect.net/german-federation/ In case you havn't yet read about it, please find below what some news portals have to say about it; the last two articles are in German. Best regards, Carsten Schiefner on behalf of the ENUM WG Co-Chairs === XConnect, DE-CIX plan NGN/VoIP communications exchange http://www.telecompaper.com/news/xconnect-de-cix-plan-ngnvoip-communication… XConnect Announces Partnership with Germany's DE-CIX http://www.voipmonitor.net/2012/01/17/XConnect+Announces+Partnership+With+G… XConnect Announces Major Partnership with DE-CIX to Create Germany's First Next Generation Network/VoIP Communications Exchange http://www.prnewswire.com/news-releases/xconnect-announces-major-partnershi… XConnect, DE-CIX partner on first nextgen networkVoIP federation in Germany http://www.fierceenterprisecommunications.com/story/xconnect-de-cix-partner… XConnect Forms Partnership with DE-CIX to Create Next Generation Network/VoIP Communications Exchange in Germany http://www.techzone360.com/news/2012/01/23/6069085.htm Deutscher Internetknoten baut VoIP- und Videotelefonie-Netz auf http://www.heise.de/newsticker/meldung/Deutscher-Internetknoten-baut-VoIP-u… DE-CIX und XConnect vereinbaren Technologie-Partnerschaft http://www.portel.de/nc/nachricht/artikel/55753-de-cix-und-xconnect-vereinb…

3 4

ENUM Status
by Niall O'Reilly 02 Nov '11

02 Nov '11

Dear ENUM-WG Colleagues, As I expect that we will not have time to visit agenda item "F" during the ENUM WG session this afternoon, you'll find the traditional status report at this URL: http://ripe63.ripe.net/presentations/108-RIPE-63-ENUM-Status.pdf Best regards, Niall O'Reilly

1 0

Fwd: ENUM WG Minutes: last call closing 30 Sep 2011
by Niall O'Reilly 02 Nov '11

02 Nov '11

Dear ENUM-WG colleagues, Bernie Hoeneisen has aked for a correction to the RIPE-62 ENUM-WG minutes. If there is no objection, I'll ask the meeting support team to change the official copy. Please note the deadline for receiving any other corrections, preferably on this list, so that all WG participants can see, falls at the end of next week: Friday, 30 September. Best regards Niall O'Reilly Begin forwarded message: > From: Bernie Hoeneisen <bernie(a)ietf.hoeneisen.ch> > Date: 8 September 2011 18:25:41 GMT+01:00 > To: Niall O'Reilly <Niall.oReilly(a)ucd.ie> > Subject: Re: [enum-wg] ENUM WG Minutes: last call closing 30 Sep 2011 > message-id: <alpine.DEB.2.00.1109081851360.32692(a)softronics.hoeneisen.ch> > > Hi Niall > > How is life? > > Small editorial corrections to RIPE-62 ENUM minutes (D1: NRENUM) > > CURRENTLY: > > Bernie Hoeneisen, ucom.ch, asked if GDS is just a means of finding the other number. He added that video conferences are based on H323 or SIP and that GDS has not been supported for five years but is still there. > > > SHOULD BE: > > Bernie Hoeneisen, ucom.ch, commented that GDS is just a means of finding the other H.323 endpoint using a number. He added that video conferences are usually based on H.323 or SIP and that GDS has not been supported for many years but is still there. > > > cheers, > Bernie > > -- > > http://ucom.ch/ > Tech Consulting for Internet Technology > > >> Dear ENUM-WG Colleagues, >> Please check the draft minutes from the ENUM WG sessions at >> RIPE meetings 60, 61, and 62, and post any errors or omissions >> to the WG list before 12:00 UTC on Friday, 30 September next. >> You'll find the minutes at >> http://www.ripe.net/ripe/groups/wg/enum/minutes/ripe-60 >> http://www.ripe.net/ripe/groups/wg/enum/minutes/ripe-61 >> http://www.ripe.net/ripe/groups/wg/enum/minutes/ripe-62 >> I intend to ask the NCC Meeting Team to mark the current >> versions "Final" shortly after that deadline. As it happens, >> and as some of you may notice, they've already done this for >> the RIPE 60 Minutes. There was a misunderstanding at some >> stage, but it's probably not worth hunting down, as I'm sure >> events will catch up in a few weeks. >> Best regards, >> Niall O'Reilly >

1 1

ENUM WG Minutes: last call closing 30 Sep 2011
by Niall O'Reilly 02 Nov '11

02 Nov '11

Dear ENUM-WG Colleagues, Please check the draft minutes from the ENUM WG sessions at RIPE meetings 60, 61, and 62, and post any errors or omissions to the WG list before 12:00 UTC on Friday, 30 September next. You'll find the minutes at http://www.ripe.net/ripe/groups/wg/enum/minutes/ripe-60 http://www.ripe.net/ripe/groups/wg/enum/minutes/ripe-61 http://www.ripe.net/ripe/groups/wg/enum/minutes/ripe-62 I intend to ask the NCC Meeting Team to mark the current versions "Final" shortly after that deadline. As it happens, and as some of you may notice, they've already done this for the RIPE 60 Minutes. There was a misunderstanding at some stage, but it's probably not worth hunting down, as I'm sure events will catch up in a few weeks. Best regards, Niall O'Reilly

1 1

A little more news you can use on the ENUM front.
by Richard Shockey 31 Oct '11

31 Oct '11

Mandatory IP interconnection for Voice in the US >From the FCC press release. Now all you have to do is translate the number .. J Cheers! 26. IP-to-IP Interconnection. We recognize the importance of interconnection to competition and the associated consumer benefits. We anticipate that the reforms we adopt will further promote the deployment and use of IP networks, and seek comment in the accompanying FNPRM regarding the policy framework for IP-to-IP interconnection. We also make clear that even while our FNPRM is pending, we expect all carriers to negotiate in good faith in response to requests for IP-to-IP interconnection for the exchange of voice traffic. http://transition.fcc.gov/Daily_Releases/Daily_Business/2011/db1027/DOC-3106 92A1.pdf http://www.snrdenton.com/news__insights/alerts/2011-10-28_overhaul.aspx http://www.dwt.com/LearningCenter/Advisories?find=441777 Richard Shockey Shockey Consulting Chairman of the Board of Directors SIP Forum PSTN Mobile: +1 703.593.2683 < <mailto:richard(at)shockey.us> mailto:richard(at)shockey.us> skype-linkedin-facebook: rshockey101 http//www.sipforum.org

1 0

RIPE 63 ENUM WG: Draft Agenda
by Niall O'Reilly 28 Oct '11

28 Oct '11

Dear ENUM WG colleagues and RIPE NCC Meeting Team, I have to make a small correction to the agenda, and to offer apologies to Ondřej Filip, whose name I mis-spelled. I'm looking forward to seeing very many of you in Vienna next week. Best regards, Niall O'Reilly Co-Chair, RIPE ENUM WG DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT Draft Agenda, ENUM WG at RIPE-63 Hilton Vienna am Stadtpark, 14:00 Wednesday 2 November. A: Administrivia (5 min) Welcome, Scribe, Jabberwok, Microphone etiquette, Agenda B: Minutes of previous meetings Confirm result of last calls on mailing list (3 min) C: Review Action List (2 min) ENUM-AP-61.3 - [DONE] Panel discussion scheduled as item D2 D: Main presentations (55 min) D1: Progress with +351 ENUM (Lino Santos, 10 min) D2: Panel discussion on state of ENUM Panellists (in alphabetical order): . Denesh Bhabuta . Patrik Fältström . Ondřej Filip . Lino Santos . Robert Schischka . Peter Szegedi E: ENUM Operations E1: Tier-0 Report (Wolfgang Nagele, 15 min) E2: +46 rescued (Patrik Fältström, 10 min) F: Short News F1: enumdata.org update (Niall O'Reilly, mailing list only) G: Discussion on Plenary presentation: [Placeholder for 'G': nothing planned this time] X: Interaction with other working groups Y: AOB Z: Close (5 min) Summary of action items -- 15:30 Coffee --

2 1

RIPE 63 ENUM WG: Draft Agenda
by Niall O'Reilly 26 Oct '11

26 Oct '11

Dear ENUM WG colleagues and RIPE NCC Meeting Team, I'ld like let you all see the latest update to the draft agenda for the ENUM WG session at RIPE 63. As I mentioned before (and no-one objected), for better flow of the meeting, I'm minded to schedule item E before item D, and to present item F only on the mailing list. I'm looking forward to seeing very many of you in Vienna next week. Best regards, Niall O'Reilly Co-Chair, RIPE ENUM WG DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT -- DRAFT Draft Agenda, ENUM WG at RIPE-63 Hilton Vienna am Stadtpark, 14:00 Wednesday 2 November. A: Administrivia (5 min) Welcome, Scribe, Jabberwok, Microphone etiquette, Agenda B: Minutes of previous meetings Confirm result of last calls on mailing list (3 min) C: Review Action List (2 min) ENUM-AP-61.3 - [DONE] Panel discussion scheduled as item D2 D: Main presentations (55 min) D1: Progress with +351 ENUM (Lino Santos, 10 min) D2: Panel discussion on state of ENUM Panellists (in alphabetical order): . Denesh Bhabuta . Patrik Fältström . Ondrej Philipp . Lino Santos . Robert Schischka . Peter Szegedi E: ENUM Operations E1: Tier-0 Report (Wolfgang Nagele, 15 min) E2: +46 rescued (Patrik Fältström, 10 min) F: Short News F1: enumdata.org update (Niall O'Reilly, mailing list only) G: Discussion on Plenary presentation: [Placeholder for 'G': nothing planned this time] X: Interaction with other working groups Y: AOB Z: Close (5 min) Summary of action items -- 15:30 Coffee --

1 0

PGP Key signing Party at RIPE 63
by Wolfgang Nagele 26 Oct '11

26 Oct '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Apologies for duplicates] Dear colleagues, It has become a sort of tradition to have a PGP key signing party (http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html) during RIPE meetings. If you would like to take part this time during RIPE 63 in Vienna (http://ripe63.ripe.net), join us on Wednesday, 2 November 2011 at 15:30 (during the coffee break) at the registration desk. The process for the signing will be: 1. Add your public key to the keyring (http://biglumber.com/x/web?keyring=4320). In order for me to be able to print the list, the deadline for this is Wednesday, 2 November 2011 at 12:00. 2. You will be provided with a printout of the keyring. It is important that you verify your own fingerprint on it with a trusted copy of your key fingerprint. 3. After we are all gathered, we will take it in turns to read our own key fingerprint so everyone else can verify it on the printout provided. It is best to check off the fingerprints you have verified on the list. 4. Next we will verify the identity of the key owner by using a legal document (passport, driver's license, etc.). For each identity you have verified you can add another checkmark on the printout. 5. Now the official part of the party is finished and once you get back home you can download the keyring and sign each key that you validated. It is easy to identify those by having two checkmarks on the printout. You should then provide the owner of that key with your signed version and possibly upload it to a key-server. If you have any questions or problems, please feel free to contact me. You may also spread the word through other information channels. Regards, Wolfgang Nagele, RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAk6nyw8ACgkQjO7G63Byy8fhGgCdHzO5k9srWXmEXkFcU0StlRZ/ 4akAoJd9TLQej1mF+lLrPnFjXc5qNijJ =e2DN -----END PGP SIGNATURE-----

1 0

Update to DNSSEC Policy and Practice Statement (DPS)
by Wolfgang Nagele 19 Oct '11

19 Oct '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear colleagues, Today we have updated our DNSSEC Policy and Practice Statement (DPS). The most notable change to the policy has been a change to the Key Usage Period section. We have extended the usage period of a Key Signing Key (KSK) to one year from previously 6 months. You can find the updated version here: http://www.ripe.net/data-tools/dns/dnssec/dnssec-policy-and-practice-statem… Regards, Wolfgang Nagele, RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAk6fE5QACgkQjO7G63Byy8fI6ACfa+zLgmkbaP6gK98BQsX0G5HG qpEAnRI7714fx+ANIPmJkL6qBQplsft1 =auU8 -----END PGP SIGNATURE-----

1 0