IETF 100 MODERN NOTES 11-15-17

TeRI and Valid/Allocated Numbers - Jon Peterson (JP)

Refresh on TeRI
- TeRI an information model for 3 operations; acquisition, management, retrieval
- TeRI interfaces
- TeRI operations and records
- TeRI records

TeRI for Number Validity

- Focused on widely understood accepted use case - valid numbers - rather than seemingly controversial use case
- New TeRI record - allocated, with 3 values - Yes, Assigned, No 
- Yes is allocated, mostly “R” records typically blocks 
- Assigned is in use, “T” records typically individual
Henning Schulzrinne (HS) - can we cover reassigned numbers
JP - yes, would likely fit under “No”
Chris Wendt (CW) - would like history of numbers
JP - seems like a good idea, model is extensible
CW - beyond reassignment should be many other use cases
JP - agreed
HS - this is not stuff we don’t capture today, no risk of carrier/competitive concerns
- Different record categories, R-range, T-individual
- Right now it’s not hierarchical
CW - isn’t it naturally hierarchical?
HS - you can have broad characteristics of a range with individual numbers having more detail
Brian Rosen (BR) - do we want to make it North American specific, i.e., no prefixes
JP - Queries vs propagation 
- Next steps, energy and discussion, good discussion today
JP - do people agree with the use case, should we move forward and build it 
HS - we should move forward with the protocol interface, there’s need to do it and its not complicated 

TeRI Over DRiP - Chris Wendt

- Overview
- TeRI/DRiP actors
- TeRI Request/Response
- TeRI/Registry interaction model - all transactions are registry related
JP - allocation interface asks authority for a credential to do the operation
- Example interaction
- TeRI acquisition operation, this is a create operation
- TeRI management operation, like post
- TeRI retrieval operation
- TeRI-DRiP dependent operations
HS - in an authoritative registry assume registrars are trusted
CW - with distributed want to assume trusted, but verify
- Asynch vs synch TeRI-DRiP, should we make it one or the other
JP - is it put or post? 
Adam Roach (AR) - would consult Mark Nottingham
JP - important take away is things are coming together

NNP Upate - Tom McGarry

- Background - modern nationwide number portability (NNP) use case
- Recent Activity - US FCC work on NNP
- Overview of NNP draft
Not enough time for questions