PEPPERMINT BOF 71 th IETF Meeting Philadelphia, USA March 12 th , - - PowerPoint PPT Presentation

peppermint bof
SMART_READER_LITE
LIVE PREVIEW

PEPPERMINT BOF 71 th IETF Meeting Philadelphia, USA March 12 th , - - PowerPoint PPT Presentation

Consolidated Provisioning Problem Statement draft-schwartz-peppermint-problem-statement-01 Authors: D. Schwartz, R. Mahy, A. Duric, E. Lewis PEPPERMINT BOF 71 th IETF Meeting Philadelphia, USA March 12 th , 2007 Evolving Peering Relationships


slide-1
SLIDE 1

Consolidated Provisioning Problem Statement

draft-schwartz-peppermint-problem-statement-01 Authors:

  • D. Schwartz, R. Mahy, A. Duric, E. Lewis

PEPPERMINT BOF

71th IETF Meeting Philadelphia, USA March 12th, 2007

slide-2
SLIDE 2

Evolving Peering Relationships

slide-3
SLIDE 3
  • Many peering registries are being formed today
  • Standardization needed before proprietary solutions emerge
  • Operators are asking for it (use > 1 registry, avoid lock in)
  • Large consortiums
  • e.g. Cablelabls, GSMA, National LNP/CDB-UK
  • Multiple in country (Non LNP) registries

Peppermint Background

slide-4
SLIDE 4

The PEPPERMINT working group is chartered to define what data needs to be exchanged within and among Multimedia administrative domains (outside the normal scope of establishing various forms of a SIP session) and how that data should be structured provisioned and propagated.

It’s all about the exchange of data

Peppermint Problem Statement

slide-5
SLIDE 5

Provisioning Interfaces

slide-6
SLIDE 6
  • Index/Key Data
  • Prefixes
  • Variable length
  • Private/public
  • Sub/super/overlapping
  • Resolution Data
  • “Ownership” not reachability
  • Multiple “owners” possible hence multiple data sets
  • LNP considerations
  • NAPTR compatibility and general future-proofing
  • Bulk exchange considerations

Registry Data

slide-7
SLIDE 7
  • Add – Add (responsible VSP) data about a new prefix to the registry
  • Delete – Remove prefix as it no longer exists anywhere
  • Port-Out - Prefix exists but previous owner no longer responsible for it
  • Port-In – Prefix existed before and is now being assigned to new owner
  • Transfer – Port-Out followed by Port-in (reduce “failure” time)
  • Renumber - Prefix changed but associated data remains the same
  • Modify – Some other attribute of prefix modified (e.g. target URI)

Logical Operations On Registry Data

slide-8
SLIDE 8

Other Registry Attributes

  • Validity – DateTime window within which prefix is addressable
  • Needed for port-in and port-out capability
  • Number Type – Unknown, IP, PSTN, both
  • PSTN carrier code – numbers with no IP reachability
  • Fee Category – free, landline, mobile, pay
  • Media Type – voice, video, message
slide-9
SLIDE 9
  • AXFR/IXFR
  • EPP
  • Excel/FTP
  • Excel/SMTP
  • HTTPS
  • SOAP/XML
  • ESPP

Protocols (In alphabetical order)