Subject: [PEPPERMINT] Preliminary notes from the BOF

From: "Richard Shockey" <[email-masked]>
Date: Mon, 17 Mar 2008 14:34:10 -0400

Many thanks to Jason Livingood for taking notes ..

If you have additional recollection of issues etc let me know as I'll draft
the minutes up.

PEPPERMINT BoF IETF 71

Agenda
======

accepted

Charter review
==============

David: "may" use 4114 ... we "may" use a lot of things.

Ken ??: agree we "may" use a lot of things - slippery slope.

shockey proposes to remove reference to 4114

David Schwartz's concerns about "within" / "among" domains... currently says
"across".

David suggests to use "within" AND "among".

Hadriel suggest "within" and "between".

??: Maybe have presentations first, and then look into the charter?

Shockey: 2nd BoF already - identified that there is a problem here.

Jon: concerned about the "among / between" and the paragraph below that as
well.. "various" is not very precise.. doubt this is the right place to do
this charter texting. don't think we can get that agreed here.

David Schwartz speaking
==============

motivation: many peering registries formed, etc..

3 relationships.

between registries, pushing up and pushing down.

registry data 

prefix sub/super 
compatibility with ENUM
resolution data - ownership information
carrier of record, etc.
bulk considerations

logical operations on registry data

other attributes: validity
fee category...

lots of data associated with a number - not neccessarily everthing in a
registry.

Adam Uzelac: Are there "views", depending on "who is asking"?
Shockey: Would be attributes reflecting policy..

Hadriel: covers LUF _and_ LRF?

David: _very_ good question - definitely a different problem set.

Jon: Break all this into achievable chunks.

Jean-Francois - ESPP
====================

effort on ENUM-SIP server provisioning specification - intended as input
into the BoF only.

Problem: how can back office services provision data out to addressing
servers.

used the netconf structure to identify high level requirements

martin dolly: please expand beyond north america.

Sean Kent
=========

talking about design principles of ESPP. 

real time vs. bulk (file) based approach for larger changes.

most people in the room understand the problem

most of them thinks the IETF should work on this problem.

Cullen: Try to get this down to as small as possible. Any ideas on how that
could be defined?

David: Maybe start with "northbound" provisioning first, and leave out
registry-registry-Peering..

Jean-Francois: High level of charter is good - hope to not go into the same
discussions as in SPEERMINT

Daryl: agree with Jon - use the terminology from SPEERMINT - please!

CHAIR additional notes:
=======================

A. Confine first pass at Goals and Milestones to  Domain to Registry and
Registry to Local Cache

B. Eliminate references to PBX interface ..at this time. Could be scoped in
the future.

C. Registry to Registry interface also in the future.

Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
PSTN Office +1 571.434.5651 
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>

_______________________________________________
PEPPERMINT mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/peppermint