<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">This is a slight topic change, but at SIPNOC for the last few years, FCC and FCC-connected people have come and talked about the plans for transitioning. My general sense is that the they're considering adding something like an IP address to the NPAC data structure.</div><div class=""><br class=""></div><div class="">There's a new IETF working group, "Modern":</div><div class=""><blockquote type="cite" class="">This list is for discussion of systems required to support the management <br class="">of telephone numbers after traditional telephone functions have migrated to <br class="">the Internet. In particular, this list considers Internet protocol <br class="">interfaces needed to register, provision and audit data related to <br class="">telephone numbers. It is expected that discussion will also involve ongoing <br class="">development of experimental systems to implement these functions.<br class=""></blockquote><div class=""><br class=""></div>A big thrust there is to develop Internet protocols to talk to all the old-school telecom systems that have kept us going through the 1980s-present. </div><div class=""><br class=""></div><div class="">They're also talking a lot there about who "owns" telephone numbers.</div><div class=""><br class=""></div><div class="">Here are some good introductory slides from the IETF meeting in March: </div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://www.ietf.org/proceedings/92/slides/slides-92-modern-0.pdf" class="">https://www.ietf.org/proceedings/92/slides/slides-92-modern-0.pdf</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 9, 2015, at 10:46 , Pete Eisengrein <<a href="mailto:peeip989@gmail.com" class="">peeip989@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Not us.<div class=""><br class=""></div><div class="">Is this topic interesting enough to everyone to try and formalize and develop? (i.e. take it off the email list and do something more)? Maybe meet up at SIPNOC? (though that's 1/2 year away). We'd be happy to host something (say, a two-day meeting) here sooner, if there's interest.</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Dec 8, 2015 at 11:57 AM, Erik Flournoy <span dir="ltr" class=""><<a href="mailto:erik@eespro.com" target="_blank" class="">erik@eespro.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Can I get a count of how many folks have SPID? There is a process that some major carriers that were once small used to do exactly what we are describing. The routing issues happen all the time even if it's not a reseller amongst CLECs, ILEC everyday even when NPAC says the number goes to xyz the ILEC ultimately controls 75% of where the call goes on the tandem.<div class="gmail_extra"><br clear="all" class=""><div class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><br class=""></div></div></div></div></div><div class="gmail_quote"><div class=""><div class="h5">On Tue, Dec 8, 2015 at 4:34 AM, Peter E <span dir="ltr" class=""><<a href="mailto:peeip989@gmail.com" target="_blank" class="">peeip989@gmail.com</a>></span> wrote:<br class=""></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><div class="h5">Well, I think that's where Mark's Bitcoin-ish idea comes in. I'm sure he can explain it better than I can.<br class="">
<span class=""><br class="">
On Dec 8, 2015, at 00:35, Peter Beckman <<a href="mailto:beckman@angryox.com" target="_blank" class="">beckman@angryox.com</a>> wrote:<br class="">
<br class="">
Reseller C and the end user knows where the chain ends, but how do WE know<br class="">
that reseller C and end-user are honest?<br class="">
</span></div></div><span class=""><div class=""><div class="">_______________________________________________<br class="">
VoiceOps mailing list<br class="">
<a href="mailto:VoiceOps@voiceops.org" target="_blank" class="">VoiceOps@voiceops.org</a><br class="">
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank" class="">https://puck.nether.net/mailman/listinfo/voiceops</a><br class="">
</div></div></span></blockquote></div><br class=""></div></div>
</blockquote></div><br class=""></div>
_______________________________________________<br class="">VoiceOps mailing list<br class=""><a href="mailto:VoiceOps@voiceops.org" class="">VoiceOps@voiceops.org</a><br class="">https://puck.nether.net/mailman/listinfo/voiceops<br class=""></div></blockquote></div><br class=""></div></div></body></html>