
From D.Malas@cablelabs.com  Tue Feb  2 07:21:16 2010
Return-Path: <D.Malas@cablelabs.com>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 131753A693D for <speermint@core3.amsl.com>; Tue,  2 Feb 2010 07:21:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.463
X-Spam-Level: 
X-Spam-Status: No, score=-4.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zf0s+3Arxjfm for <speermint@core3.amsl.com>; Tue,  2 Feb 2010 07:21:14 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 600A83A6934 for <speermint@ietf.org>; Tue,  2 Feb 2010 07:21:14 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o12FLqNR001565 for <speermint@ietf.org>; Tue, 2 Feb 2010 08:21:52 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Tue, 2 Feb 2010 08:21:52 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Tue, 2 Feb 2010 08:21:52 -0700
From: Daryl Malas <D.Malas@cablelabs.com>
To: "speermint@ietf.org" <speermint@ietf.org>
Date: Tue, 2 Feb 2010 08:21:51 -0700
Thread-Topic: [Speermint] FW: 77th IETF - Hotel and Registration Information 
Thread-Index: AcqkGjqmHLPJ8/N4RVqaDXP/lQsgAwAARO0w
Message-ID: <114DAD31379DFA438C0A2E39B3B8AF5D01213F655E@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Subject: [Speermint]  FW: 77th IETF - Hotel and Registration Information
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 15:21:16 -0000

FYI...We hope to see you in Anaheim.

--Speermint Chairs

-----Original Message-----
Subject: 77th IETF - Hotel and Registration Information=20

77th IETF Meeting
Anaheim, CA, USA
March 21-26, 2010=20
=20
Registration is now open!=20
=20
Register online at: http://www.ietf.org/meetings/77/=20
=20
1. Registration Types
2. Visas and Letters of Invitation
3. Accommodations & Breakfast Information - Cutoff February 26, 2010
=20
1) Registration Types=20
=20
A. Early-Bird Registration - USD 635.00 Register and pay before Friday, 12 =
March 2010 at 17:00 PST (24:00 UTC) for Early-Bird rate.=20
=20
B. After Early-Bird cutoff - USD 785.00=20
=20
C. Full-time Student Registrations - USD 150.00 Full-time students with pro=
per ID are eligible to receive a special USD 150.00 student rate. Student r=
ate is not subject to any late-fees.=20
Students will also be able to register on-site at the special student rate.=
 Failure to provide valid student ID on-site will revoke the special studen=
t status.=20
=20
D. One Day Pass Registration - USD 200.00 We are once again offering a one-=
day pass for $200. Benefits are:=20
=20
1. Attend all sessions during any one day of the Meeting, and partake of th=
e food and beverage during the breaks 2. You select which day to attend whe=
n you show up onsite to check-in 3. Payments may be made onsite without a l=
ate fee 4. Pass can be upgraded to a full Meeting Registration, however, la=
te fee may apply if initial one-day payment not made before Early Bird dead=
line 5. Attend Sunday Tutorials at no additional charge 6. Attend Sunday We=
lcome Reception at no additional charge 7. Attend Wednesday and Thursday Pl=
enaries at no additional charge=20
=20
CANCELLATION
The cut-off for registration cancellation is Monday, 15 March 2010 at 17:00=
 PT (01:00 Tuesday, March 16 UTC). Cancellations are subject to a 10% (ten =
percent) cancellation fee.=20
=20
Online Registration ends: Friday, 19 March, 2010 at 17:00 PT (24:00 UTC)=20
=20
On-site Registration
You can register onsite at the meeting in Anaheim, CA, USA starting Sunday,=
 21 March 2010 at 12:00 noon PT.=20
=20
Meeting Schedule: Start Monday morning and run through Friday at 15:15 loca=
l time. Most training sessions will take place on Sunday afternoon 21 March=
 2010. Participants should plan their travel accordingly.=20
=20
2) Letters of Invitation and Visas=20
=20
Letters of Invitation
After you complete the meeting registration process, you will be given the =
option to request an IETF letter of invitation. =20
=20
Visas
We recommend you allocate at least one month to complete the visa process.
See here for more information on the visa application process: =20
https://esta.cbp.dhs.gov=20
=20
The following countries participate in the Visa Waiver Program (as of Decem=
ber 30, 2008):=20
Andorra, Australia, Austria, Belgium, Brunei, Czech Republic, Denmark, Esto=
nia, Finland, France, Germany, Hungary, Iceland, Ireland, Italy, Japan, Lat=
via, Liechtenstein, Lithuania, Luxembourg, Malta, Monaco, the Netherlands, =
New Zealand, Norway, Portugal, San Marino, Singapore, Slovakia, Slovenia, S=
outh Korea, Spain, Sweden, Switzerland, and the United Kingdom=20
=20
Applications may be submitted at any time prior to travel to the United Sta=
tes. The Department of Homeland Security recommends that travel authorizati=
on applications be submitted at least 72 hours prior to travel.
Unless revoked, travel authorizations are valid for two years from the date=
 of authorization, or until your passport expires, whichever comes first.=20
=20
You can update the following information at https://esta.cbp.dhs.gov once y=
ou have received approval:=20
- Email address
- Telephone number
- Airline and flight number
- City where you are boarding
- Address while in the United States=20
=20
3) Accommodations & Breakfast Information The IETF has a sleeping room bloc=
k at the main IETF 77 meeting venue: the Hilton Anaheim. Room rate is $194 =
USD single and $214 USD double plus 15% per room per night and $1.15 USD pe=
r room per night tax. More information about the hotel can be found here:=20
http://www.ietf.org/meeting/77/hotel.html.=20
Breakfast will be provided as part of the on-site meeting services.=20
=20
Only 47 days until IETF 77!=20
=20

From bernie@ietf.hoeneisen.ch  Wed Feb 24 06:20:32 2010
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3782A28C181; Wed, 24 Feb 2010 06:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level: 
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pttvnmvr4FM4; Wed, 24 Feb 2010 06:20:31 -0800 (PST)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) by core3.amsl.com (Postfix) with ESMTP id B5F9728C108; Wed, 24 Feb 2010 06:20:30 -0800 (PST)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.69) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1NkI8K-0003dg-2N; Wed, 24 Feb 2010 15:22:36 +0100
Date: Wed, 24 Feb 2010 15:22:36 +0100 (CET)
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: drinks@ietf.org, speermint@ietf.org
Message-ID: <alpine.DEB.2.00.1002241521280.10552@softronics.hoeneisen.ch>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="37663318-1922192837-1267020046=:10552"
Content-ID: <alpine.DEB.2.00.1002241521281.10552@softronics.hoeneisen.ch>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Subject: [Speermint] [e2md] charter discussion kick-off (fwd)
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 14:20:32 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--37663318-1922192837-1267020046=:10552
Content-Type: TEXT/PLAIN; FORMAT=flowed; CHARSET=US-ASCII
Content-ID: <alpine.DEB.2.00.1002241521282.10552@softronics.hoeneisen.ch>

Dear speermint / drinks participant

For the E2MD (E.164 To MetaData) BoF during IETF-77 in Anheim we are 
currently discussing the charter proposal. As e2md is closely related
to what you are defining in DRINKS and SPEERMINT, we kindly ask you to 
review the charter and provide feedback to the <e2md@ietf.org> list
by the end of this month (Feb 2010).

Looking forward to a fruitful discussion!

cheers,
  Bernie


---------- Forwarded message ----------
Date: Wed, 24 Feb 2010 15:00:46
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
To: E.164 To MetaData BOF discussion list <e2md@ietf.org>
Subject: [e2md] charter discussion kick-off

Hi,

After we have collected the use cases, the e2md work continues with the
charter.

To ensure we have no (unknown) open issues with the charter during the BoF, we 
kindly ask you to review the proposal for the e2md charter. The latest version 
can be found on:

   http://ucom.ch/ietf/e2md-bof/e2md-proposed-charter.txt

For your convenience I attached the current version to this email.

Please send any feedback, issues and other comments concerning the proposed 
e2md charter to <e2md@ietf.org> by the end of this month (Feb 2010).

cheers,
  Bernie

--

http://ucom.ch/
Tech Consulting for Internet Standardization
--37663318-1922192837-1267020046=:10552
Content-Type: TEXT/PLAIN; NAME=e2md-proposed-charter.txt
Content-Transfer-Encoding: BASE64
Content-ID: <alpine.DEB.2.00.1002241500460.10552@softronics.hoeneisen.ch>
Content-Description: 
Content-Disposition: ATTACHMENT; FILENAME=e2md-proposed-charter.txt

RS4xNjQgdG8gTWV0YURhdGEgKEUyTUQpIChwcm9wb3NlZCBjaGFydGVyKQ0K
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCkxhc3QgTW9kaWZpZWQ6IDIw
MTAtMDItMjQNCg0KQWRkaXRpb25hbCBpbmZvcm1hdGlvbiBpcyBhdmFpbGFi
bGUgYXQgdG9vbHMuaWV0Zi5vcmcvd2cvZTJtZA0KW25vdCB5ZXQgaW4gdXNl
XQ0KDQoNCkNoYWlyKHMpOg0KDQogICAgKiBUQkENCg0KUmVhbC10aW1lIEFw
cGxpY2F0aW9ucyBhbmQgSW5mcmFzdHJ1Y3R1cmUgQXJlYSBEaXJlY3Rvcihz
KToNCg0KICAgICogUm9iZXJ0IFNwYXJrcyA8cmpzcGFya3NAbm9zdHJ1bS5j
b20+DQogICAgKiBDdWxsZW4gSmVubmluZ3MgPGZsdWZmeUBjaXNjby5jb20+
DQoNClJlYWwtdGltZSBBcHBsaWNhdGlvbnMgYW5kIEluZnJhc3RydWN0dXJl
IEFyZWEgQWR2aXNvcjoNCg0KICAgICogQ3VsbGVuIEplbm5pbmdzIDxmbHVm
ZnlAY2lzY28uY29tPg0KDQoNCk1haWxpbmcgTGlzdHM6DQoNCkdlbmVyYWwg
RGlzY3Vzc2lvbjogZTJtZEBpZXRmLm9yZw0KTGlzdGluZm86IGh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZTJtZA0KVG8gU3Vic2Ny
aWJlOiBlMm1kLXJlcXVlc3RAaWV0Zi5vcmcNCkluIEJvZHk6IHN1YnNjcmli
ZQ0KQXJjaGl2ZTogaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUv
d2ViL2UybWQvaW5kZXguaHRtbA0KDQoNCg0KRGVzY3JpcHRpb24gb2YgV29y
a2luZyBHcm91cDoNCg0KQWJzdHJhY3QNCg0KICAgRS4xNjQgdG8gTWV0YURh
dGEgKEUyTUQpIHdpbGwgdXNlIG9mIHRoZSBEb21haW4gTmFtZSBTeXN0ZW0g
KEROUykNCiAgIGZvciByZXNvbHZpbmcgRS4xNjQgbnVtYmVycyBpbnRvIG1l
dGFkYXRhIHRvIHByb3ZpZGUgaW5mb3JtYXRpb24NCiAgIGFib3V0IEUuMTY0
IG51bWJlcnMgaW4gY2FzZXMgd2hlcmUgRS4xNjQgTnVtYmVyIHRvIFVSSSBN
YXBwaW5nDQogICAoRU5VTSkgY2FuIG5vdCBiZSB1c2VkLg0KDQoNCkJhY2tn
cm91bmQNCg0KICAgRU5VTSBwcm92aWRlcyBhbiBpZGVudGlmaWVyIG1hcHBp
bmcgbWVjaGFuaXNtIHRvIG1hcCBFLjE2NCBudW1iZXJzDQogICB0byBVbmlm
b3JtIFJlc291cmNlIElkZW50aWZpZXJzIChVUklzKSB1c2luZyB0aGUgRE5T
Lg0KDQogICBUaHVzLCBFTlVNIGNhbiBiZSB1c2VkIHRvIGxvb2sgdXAgdGhl
IHNlcnZpY2VzIGFzc29jaWF0ZWQgd2l0aCBhbg0KICAgRS4xNjQgbnVtYmVy
LiAgSG93ZXZlciwgaXQgaXMgY29udHJvdmVyc2lhbCB3aGV0aGVyIG9yIG5v
dCB0aGUgcmVzdWx0DQogICBvZiBhbiBFTlVNIGxvb2t1cCBzaG91bGQgYWx3
YXlzIGJlIGludGVuZGVkIHRvIGVzdGFibGlzaCBhDQogICBjb21tdW5pY2F0
aW9ucyBzZXNzaW9uIHVzaW5nIHRoZSBVUkkgZm91bmQgaW4gdGhlIGNvcnJl
c3BvbmRpbmcNCiAgIE5hbWluZyBBdXRob3JpdHkgUG9pbnRlciAoTkFQVFIp
IEROUyBSZXNvdXJjZSBSZWNvcmQgKFJSKS4NCg0KDQpQcm9ibGVtIFN0YXRl
bWVudA0KDQogICBTZXZlcmFsIHByb3Bvc2FscyBmb3IgRW51bXNlcnZpY2Ug
cmVnaXN0cmF0aW9ucyBkbyBub3QgZnVsZmlsbCB0aGUNCiAgIGFib3ZlIG1l
bnRpb25lZCBpbnRlcnByZXRhdGlvbiwgd2hpY2ggc3VnZ2VzdHMgdGhhdCBh
biBFTlVNIGxvb2t1cA0KICAgc2hvdWxkIGFsd2F5cyBiZSBpbnRlbmRlZCB0
byByZXN1bHQgaW4gYSBjb21tdW5pY2F0aW9ucyBzZXNzaW9uLg0KICAgVGhl
c2UgcHJvcG9zYWxzIGFyZSB0aGVyZWZvcmUgdmlydHVhbGx5IGxvY2tlZCBp
biB0aGUgcHJvY2Vzcy4NCiAgIFN1Y2ggcHJvcG9zYWxzIGluY2x1ZGUgKGJ1
dCBhcmUgbm90IGxpbWl0ZWQgdG8pIEVudW1zZXJ2aWNlcyBmb3INCiAgICdj
bmFtJyB0byBwcm92aWRlIGluZm9ybWF0aW9uIGFib3V0IHRoZSBjYWxsaW5n
IHBhcnR5IG5hbWUsDQogICAndW51c2VkJyB0byBwcm92aWRlIGEgaGludCB0
aGF0IGEgbnVtYmVyIGlzIG5vdCBpbiB1c2UsIGFuZA0KICAgJ3NlbmQtbicg
dG8gZGVzY3JpYmUgdGhlIHN0cnVjdHVyZSBvZiBhbiBFTlVNIHRyZWUuDQoN
CiAgIEFub3RoZXIgaXNzdWUgaXMgdGhhdCB0aGUgcmVzdWx0IG9mIGFuIEVO
VU0gKEUyVSkgbG9va3VwIGFsd2F5cw0KICAgbmVlZHMgdG8gYmUgYW4gVVJJ
LCB3aGljaCB1bm5lY2Vzc2FyaWx5IGNvbXBsaWNhdGVzIHNpbXBsZSBtYXBw
aW5ncy4NCg0KICAgVGhlIGF1dGhvcnMgb2Ygc3VjaCBFbnVtc2VydmljZSBw
cm9wb3NhbHMgdHJpZWQgdG8gY2lyY3VtdmVudCB0aGUNCiAgIGlzc3VlcyBi
eSBpbnRyb2R1Y2luZyB0aGUgJ2RhdGEnIFVSSSBzY2hlbWUgb3IgaW52ZW50
aW5nIGNvbXBsZXRlbHkNCiAgIG5ldyBVUkkgc2NoZW1lcywgd2l0aCBsaW1p
dGVkIHN1Y2Nlc3MgaG93ZXZlci4gIFRoZSBtYWluIG9iamVjdGlvbg0KICAg
cmVtYWluZWQgdGhhdCBhbiBFTlVNIGxvb2t1cCBzaG91bGQgYWx3YXlzIHJl
c3VsdCBpbiBhIFVSSSBpbnRlbmRlZA0KICAgdG8gZXN0YWJsaXNoIGEgY29t
bXVuaWNhdGlvbnMgc2Vzc2lvbi4NCg0KUHJvcG9zYWwNCg0KICAgVGhlIEUy
TUQgV29ya2luZyBHcm91cCBpcyBjaGFydGVyZWQgdG8gZGV2ZWxvcCBhIG5l
dyBEeW5hbWljDQogICBEZWxlZ2F0aW9uIERpc2NvdmVyeSBTeXN0ZW0gKERE
RFMpIGFwcGxpY2F0aW9uIEUyTUQsIHdoaWNoIGNhbiBiZQ0KICAgdXNlZCB3
aXRoIEROUyBOQVBUUiBSUnMgZm9yIHJlc29sdmluZyBFLjE2NCBudW1iZXJz
IGludG8gbWV0YWRhdGEuDQogICBUaGUgcmVzdWx0aW5nIG1ldGFkYXRhIGNh
biBiZSB1c2VkIChmb3IgZXhhbXBsZSkgdG8gcHJvdmlkZSBoaW50cw0KICAg
YWJvdXQgcHJvcGVydGllcyBvZiBjZXJ0YWluIEVOVU0gZG9tYWlucyBvciB0
byBwcm92aWRlIGluZm9ybWF0aW9uDQogICB0aGF0IGNhbiBiZSB1c2VkIGFz
IGF0dHJpYnV0ZXMgb2YgYW4gRS4xNjQgbnVtYmVyLg0KDQogICBFMk1EIHdp
bGwgcHJvdmlkZSB0aGUgbWVhbnMgZm9yIHNlcnZpY2VzIHJlbGF0ZWQgdG8g
RS4xNjQgbnVtYmVycw0KICAgdGhhdCBkbyBub3QgZml0IGludG8gdGhlIGNv
bmNlcHQgb2YgRU5VTSAoRTJVKSwgYW5kIHRodXMgYQ0KICAgd2F5IGZvcndh
cmQgZm9yIHN1Y2ggZXhpc3RpbmcgRU5VTSBXRyBkb2N1bWVudHMgaW4gdGhl
IHF1ZXVlLg0KDQogICBBbG9uZyB3aXRoIHRoZSBFMk1EIERERFMgYXBwbGlj
YXRpb24gYSBuZXcgSUFOQSByZWdpc3RyeSB3aWxsIGJlDQogICBzcGVjaWZp
ZWQgZm9yIHJlZ2lzdHJhdGlvbiBvZiBFMk1EIHNlcnZpY2VzLiBUaGUgcmVn
aXN0cmF0aW9uIHBvbGljeQ0KICAgc2hhbGwgYmUgRXhwZXJ0IFJldmlldyBh
bmQgU3BlY2lmaWNhdGlvbiBSZXF1aXJlZCAoc2VlIFJGQyA1MjI2KSwNCiAg
IHNpbWlsYXJseSBhcyBzcGVjaWZpZWQgZm9yIEVudW1zZXJ2aWNlIHJlZ2lz
dHJhdGlvbnMuDQoNCiAgIFRoZSBFMk1EIHNwZWNpZmljYXRpb25zIHNoYWxs
IHJldXNlIGEgbXVjaCBhcyBwb3NzaWJsZSBmcm9tIHRoZSBFTlVNDQogICBE
RERTIGFuZCBpdHMgSUFOQSByZWdpc3RyeSBzcGVjaWZpY2F0aW9uLg0KDQog
ICBUaGUgRTJNRCBXb3JraW5nIEdyb3VwIG1heSB0YWtlIG9uIGZ1cnRoZXIg
cHJvcG9zYWxzIGZvciBFMk1EIHNlcnZpY2UNCiAgIHJlZ2lzdHJhdGlvbnMg
KGUuZy4gc2VuZC1uKSB1bnRpbCB0aGUgSUFOQSByZWdpc3RyYXRpb24gZm9y
IEUyTUQNCiAgIHNlcnZpY2VzIGlzIGFwcHJvdmVkIGJ5IHRoZSBJRVNHLg0K
DQoNCk91dC1PZi1TY29wZQ0KDQogICBFMk1EIHNoYWxsIG5vdCBiZSBzcGVj
aWZpZWQgYXMgYSBnZW5lcmFsIHB1cnBvc2UgbG9va3VwIG5vciBhcyBidWxr
DQogICB0cmFuc2ZlciBwcm90b2NvbCwgYnV0IHJhdGhlciBmb2N1cyBvbiBj
bGVhciB1c2UgY2FzZXMgcmVsYXRlZCB0bw0KICAgRS4xNjQgbnVtYmVycy4N
Cg0KDQpHb2FscyBhbmQgTWlsZXN0b25lczoNCg0KICAgQXVnIDIwMTAgIFN1
Ym1pdCBJbnRlcm5ldCBEcmFmdChzKSBmb3IgdGhlIEUyTUQgREREUyBhcHBs
aWNhdGlvbiBhbmQNCiAgICAgICAgICAgICBpdHMgSUFOQSByZWdpc3RyeSBz
cGVjaWZpY2F0aW9uDQoNCiAgIERlYyAyMDEwICBTdWJtaXQgJ2NuYW0nIGFu
ZCAndW51c2VkJyBhcyBFMk1EIHNlcnZpY2UgcmVnaXN0cmF0aW9ucw0KICAg
ICAgICAgICAgIChJbmZvcm1hdGlvbmFsKQ0KDQogICBYWFggMjAxMSAgQ2xv
c2UgdGhlIEUyTUQgV29ya2luZyBHcm91cCAob3IgcmVjaGFydGVyKQ0KDQoN
CkludGVybmV0LURyYWZ0czoNCg0KICAgaHR0cDovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtaG9lbmVpc2VuLWUxNjQtdG8tbWV0YWRhdGEtMDINCiAg
IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtZW51bS11
bnVzZWQtMDQNCiAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWlldGYtZW51bS1jbmFtLTA4DQogICAoaHR0cDovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtYmVsbGlzLWVudW0tc2VuZC1uLTAyKQ0KDQoNClJlcXVl
c3QgRm9yIENvbW1lbnRzOg0KDQogICBOb25lDQoNCg==

--37663318-1922192837-1267020046=:10552
Content-Type: TEXT/PLAIN; CHARSET=us-ascii
Content-ID: <alpine.DEB.2.00.1002241521283.10552@softronics.hoeneisen.ch>
Content-Description: 
Content-Disposition: INLINE

_______________________________________________

e2md mailing list

e2md@ietf.org

https://www.ietf.org/mailman/listinfo/e2md


--37663318-1922192837-1267020046=:10552--

From alexander.mayrhofer@enum.at  Wed Feb 24 08:26:37 2010
Return-Path: <alexander.mayrhofer@enum.at>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2ED5E3A83F6 for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 08:26:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEIml6LKtoHt for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 08:26:36 -0800 (PST)
Received: from na.nona.net (engine01.malakii.net [188.40.65.119]) by core3.amsl.com (Postfix) with ESMTP id 415823A83F3 for <speermint@ietf.org>; Wed, 24 Feb 2010 08:26:34 -0800 (PST)
Received: from [10.10.0.134] ([::ffff:83.136.33.3]) (AUTH: PLAIN axelm, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by kahua with esmtp; Wed, 24 Feb 2010 17:28:39 +0100 id 00000000001546FA.000000004B8553B7.000003F8
Message-ID: <4B855392.3080900@enum.at>
Date: Wed, 24 Feb 2010 17:28:02 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Organization: enum.at GmbH
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: speermint@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Speermint] Clarification sought about LUF response data.
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 16:26:37 -0000

As you probably know, DRINKS is working on a protocol that allows for
provisioning of data which is then returned as Session Establishment
Data in the chain of the LUF/LRF functions.

We're currently discussion what type of data the LUF should return (and
therefore, what type/kind of data is used as input data for the LRF).

The SPEERMINT documents are not consistent and entirely clear about
this. I'm right now looking only at RFC5486 (which is the most relevant
document for terminology, obviously), and even that document contradicts
itself in the definition (Section 4.3.3):

  "The Look-Up Function (LUF) determines for a given request the target
   domain to which the request should be routed.  An example of an LUF
   is an ENUM [4] look-up or a SIP INVITE request to a SIP proxy
   providing redirect responses for peers."

The first sentence says "it returns a domain", while the examples in the
second sentence indicate that it would return a full AoR? I know that a
sip: URI does not need to contain a user part, but it seems the much
more common case that ENUM or SIP redirect servers return sip: URIs
including a user part.

Looking at the ENUM and SIP redirect cases specifically, we think that a
typical useful LUF response would be as follows:

  tel:+19195551234 -> LUF -> sip:+19195551234@voip.example.com

rather than

  tel:+19195551234 -> LUF -> sip:voip.example.com

I think that the question is whether or not the LUF response *replaces*
the original URI, or rather *amends* it with the additional information.

It's also related to the question what data is fed into the LRF? Is the
only data fed into that function the response data from the LUF, or is
it both the LUF response plus the original URI, eg.:

 tel:+19195551234
   plus               ----> LRF --->  sip:9195551234@192.168.2.12:123
 sip:voip.example.com

With the "domain only" LUF response alone, the LRF could just return a
"generic" SF address that requires additional information to properly
route the session:

sip:voip.example.com  ----> LRF ----> sip:sbc@192.168.2.12:1234

Therefore, it seems to us cleaner when the LUF returns a full AoR. It
would still fit the definition of "determining the target domain", it
just "copies" certain information from the input data to the output data.

Opinions and comments to clarify that?

Alex

From D.Hancock@CableLabs.com  Wed Feb 24 09:53:03 2010
Return-Path: <D.Hancock@CableLabs.com>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA12228C21E for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 09:53:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.273
X-Spam-Level: 
X-Spam-Status: No, score=-0.273 tagged_above=-999 required=5 tests=[AWL=0.190,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13UL2gos0bbH for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 09:53:03 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 10DC528C204 for <speermint@ietf.org>; Wed, 24 Feb 2010 09:53:03 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o1OHt9Ii022900 for <speermint@ietf.org>; Wed, 24 Feb 2010 10:55:09 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Wed, 24 Feb 2010 10:55:09 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Wed, 24 Feb 2010 10:55:10 -0700
From: David Hancock <D.Hancock@CableLabs.com>
To: "speermint@ietf.org" <speermint@ietf.org>
Date: Wed, 24 Feb 2010 10:55:09 -0700
Thread-Topic: Should SIP Interconnect Guidelines recommend Transmission Loss?
Thread-Index: Acq1eoFba/pGrqW/TvC16ibYoYb92g==
Message-ID: <76AC5FEF83F1E64491446437EA81A61F7CD4B2B65A@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Subject: [Speermint] Should SIP Interconnect Guidelines recommend Transmission Loss?
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 17:53:04 -0000

The current version of SPEERMINT draft-hancock-sip-interconnect-guidelines-=
02 places transmission loss out-of-scope. I'd like to propose that we move =
this to in-scope. I think this is important because the transmission loss i=
nserted by both peering networks contributes to the end-to-end loss of the =
media connection. Improper end-to-end loss settings can affect voice qualit=
y (too loud/soft, annoying echo), and the ability of the connection to conv=
ey voice-band data such as DTMF digits.

Does everyone agree this should be placed in-scope?=20

If yes, what is the requirement? My thought is that we recommend support of=
 TIA-912B at a minimum (and possibly ETSI ES 202 020 for international netw=
orks). There are other standards that affect the Overall Loudness Rating (O=
LR) of the media connection (e.g., TIA-470 specifies the SLR/RLR for analog=
 handsets). Should we include these additional standards as well, or assume=
 they get pulled in by TIA-912B (since 912B does informatively reference th=
ese other documents)? =20

Thanks
David

From pp3129@att.com  Wed Feb 24 10:05:44 2010
Return-Path: <pp3129@att.com>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0471228C267 for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 10:05:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XbRNaP8A6wsm for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 10:05:43 -0800 (PST)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id EDA6D28C256 for <speermint@ietf.org>; Wed, 24 Feb 2010 10:05:42 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: pp3129@att.com
X-Msg-Ref: server-10.tower-146.messagelabs.com!1267034861!10380869!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 9260 invoked from network); 24 Feb 2010 18:07:41 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-10.tower-146.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 24 Feb 2010 18:07:41 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o1OI7Vfm013106 for <speermint@ietf.org>; Wed, 24 Feb 2010 13:07:32 -0500
Received: from gaalpa1msgusr7a.ugd.att.com (gaalpa1msgusr7a.ugd.att.com [135.53.26.15]) by mlpd194.enaf.sfdc.sbc.com (8.14.3/8.14.3) with ESMTP id o1OI7RMf013000 for <speermint@ietf.org>; Wed, 24 Feb 2010 13:07:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 24 Feb 2010 13:07:35 -0500
Message-ID: <35FE871E2B085542A35726420E29DA6B036CCFB8@gaalpa1msgusr7a.ugd.att.com>
In-Reply-To: <76AC5FEF83F1E64491446437EA81A61F7CD4B2B65A@srvxchg>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] Should SIP Interconnect Guidelines recommendTransmission Loss?
Thread-Index: Acq1eoFba/pGrqW/TvC16ibYoYb92gAAQMCw
References: <76AC5FEF83F1E64491446437EA81A61F7CD4B2B65A@srvxchg>
From: "PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com>
To: "David Hancock" <D.Hancock@CableLabs.com>, <speermint@ietf.org>
Subject: Re: [Speermint] Should SIP Interconnect Guidelines recommendTransmission Loss?
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 18:05:44 -0000

David:
I do not believe in IP interconnection we should be involved in
manipulating loss. I see that as more a CPE or gateway function where
conversion to analog is taking place. I see this has separate from the
(IP) NNI.=20

Penn Pfautz
AT&T Access Management
+1-732-420-4962

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On
Behalf Of David Hancock
Sent: Wednesday, February 24, 2010 12:55 PM
To: speermint@ietf.org
Subject: [Speermint] Should SIP Interconnect Guidelines
recommendTransmission Loss?

The current version of SPEERMINT
draft-hancock-sip-interconnect-guidelines-02 places transmission loss
out-of-scope. I'd like to propose that we move this to in-scope. I think
this is important because the transmission loss inserted by both peering
networks contributes to the end-to-end loss of the media connection.
Improper end-to-end loss settings can affect voice quality (too
loud/soft, annoying echo), and the ability of the connection to convey
voice-band data such as DTMF digits.

Does everyone agree this should be placed in-scope?=20

If yes, what is the requirement? My thought is that we recommend support
of TIA-912B at a minimum (and possibly ETSI ES 202 020 for international
networks). There are other standards that affect the Overall Loudness
Rating (OLR) of the media connection (e.g., TIA-470 specifies the
SLR/RLR for analog handsets). Should we include these additional
standards as well, or assume they get pulled in by TIA-912B (since 912B
does informatively reference these other documents)? =20

Thanks
David
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint

From D.Malas@cablelabs.com  Wed Feb 24 10:09:32 2010
Return-Path: <D.Malas@cablelabs.com>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC82A28C1B9 for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 10:09:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.463
X-Spam-Level: 
X-Spam-Status: No, score=-2.463 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z6njLXsWDaue for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 10:09:32 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 0C2AA28C143 for <speermint@ietf.org>; Wed, 24 Feb 2010 10:09:31 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o1OIBXRM024439; Wed, 24 Feb 2010 11:11:33 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Wed, 24 Feb 2010 11:11:33 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Wed, 24 Feb 2010 11:11:33 -0700
From: Daryl Malas <D.Malas@cablelabs.com>
To: "'Alexander Mayrhofer'" <alexander.mayrhofer@enum.at>, "speermint@ietf.org" <speermint@ietf.org>
Date: Wed, 24 Feb 2010 11:11:32 -0700
Thread-Topic: [Speermint] Clarification sought about LUF response data.
Thread-Index: Acq1bnF8ai3oVob8S+OaSQfWcI81/QADM1ZA
Message-ID: <114DAD31379DFA438C0A2E39B3B8AF5D01213F6663@srvxchg>
References: <4B855392.3080900@enum.at>
In-Reply-To: <4B855392.3080900@enum.at>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Subject: Re: [Speermint] Clarification sought about LUF response data.
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 18:09:33 -0000

Alex,

The purpose of the definition is to say for a given request, +13035551212, =
the LUF determines the target domain, ssp.example.com; which, results in +1=
3035551212@ssp.example.com.  The LRF determines for ssp.example.com the app=
ropriate path to get there, for example:

$ORIGIN _sip._udp.ssp.example.com.
	IN   SRV  0   1   5060    big-sbe.ssp.example.com
	IN   SRV  1   1   5060    small-sbe.ssp.example.com
	IN   SRV  1   2   5060    old-big-sbe.ssp.example.com
big-sbe	A  192.168.5.5
small-sbe	A  192.168.4.5
old-big-sbe	A  192.168.100.5

Or, the LRF may return an egress route as described in draft-malas-enum-tru=
nk-sip-01, for example:=20

$ORIGIN 2.1.2.1.5.5.5.3.0.3.1.e164.arpa.
      NAPTR 10 100 "u" "E2U+sip"  "!^.*$!sip:\1;tgrp=3DTG-1;trunk-context=
=3Dssp2.example.com  @big-sbe.ssp.example.com;user=3Dphone!" .


Regards,

Daryl=20

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Alexander Mayrhofer
Sent: Wednesday, February 24, 2010 9:28 AM
To: speermint@ietf.org
Subject: [Speermint] Clarification sought about LUF response data.


As you probably know, DRINKS is working on a protocol that allows for provi=
sioning of data which is then returned as Session Establishment Data in the=
 chain of the LUF/LRF functions.

We're currently discussion what type of data the LUF should return (and the=
refore, what type/kind of data is used as input data for the LRF).

The SPEERMINT documents are not consistent and entirely clear about this. I=
'm right now looking only at RFC5486 (which is the most relevant document f=
or terminology, obviously), and even that document contradicts itself in th=
e definition (Section 4.3.3):

  "The Look-Up Function (LUF) determines for a given request the target
   domain to which the request should be routed.  An example of an LUF
   is an ENUM [4] look-up or a SIP INVITE request to a SIP proxy
   providing redirect responses for peers."

The first sentence says "it returns a domain", while the examples in the se=
cond sentence indicate that it would return a full AoR? I know that a
sip: URI does not need to contain a user part, but it seems the much more c=
ommon case that ENUM or SIP redirect servers return sip: URIs including a u=
ser part.

Looking at the ENUM and SIP redirect cases specifically, we think that a ty=
pical useful LUF response would be as follows:

  tel:+19195551234 -> LUF -> sip:+19195551234@voip.example.com

rather than

  tel:+19195551234 -> LUF -> sip:voip.example.com

I think that the question is whether or not the LUF response *replaces* the=
 original URI, or rather *amends* it with the additional information.

It's also related to the question what data is fed into the LRF? Is the onl=
y data fed into that function the response data from the LUF, or is it both=
 the LUF response plus the original URI, eg.:

 tel:+19195551234
   plus               ----> LRF --->  sip:9195551234@192.168.2.12:123
 sip:voip.example.com

With the "domain only" LUF response alone, the LRF could just return a "gen=
eric" SF address that requires additional information to properly route the=
 session:

sip:voip.example.com  ----> LRF ----> sip:sbc@192.168.2.12:1234

Therefore, it seems to us cleaner when the LUF returns a full AoR. It would=
 still fit the definition of "determining the target domain", it just "copi=
es" certain information from the input data to the output data.

Opinions and comments to clarify that?

Alex
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint

From hmmr@cisco.com  Wed Feb 24 19:39:20 2010
Return-Path: <hmmr@cisco.com>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DCA43A861B for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 19:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxhpgdfrfXFl for <speermint@core3.amsl.com>; Wed, 24 Feb 2010 19:39:19 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 1EE5F3A861A for <speermint@ietf.org>; Wed, 24 Feb 2010 19:39:19 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEABuAhUutJV2d/2dsb2JhbACbFHOkEphMhHIEgxY
X-IronPort-AV: E=Sophos;i="4.49,536,1262563200"; d="scan'208";a="242384099"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by sj-iport-2.cisco.com with ESMTP; 25 Feb 2010 03:41:28 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id o1P3fR46011064;  Thu, 25 Feb 2010 03:41:27 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 24 Feb 2010 21:41:28 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 24 Feb 2010 21:41:26 -0600
Message-ID: <C4064AF1C9EC1F40868C033DB94958C7F0EDA2@XMB-RCD-111.cisco.com>
In-Reply-To: <4B855392.3080900@enum.at>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Speermint] Clarification sought about LUF response data.
Thread-Index: Acq1boljD7O5COPGT/60mTP61FYK/QAXVE5Q
References: <4B855392.3080900@enum.at>
From: "Mike Hammer (hmmr)" <hmmr@cisco.com>
To: "Alexander Mayrhofer" <alexander.mayrhofer@enum.at>, <speermint@ietf.org>
X-OriginalArrivalTime: 25 Feb 2010 03:41:28.0073 (UTC) FILETIME=[69754790:01CAB5CC]
Subject: Re: [Speermint] Clarification sought about LUF response data.
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 03:39:20 -0000

Alex,

While I like your idea that the LUF should expand the tel URI to create
the sip URI by adding the domain,
it seemed ambiguous what you want the LRF was to return in that case.

I would prefer that the LRF use the domain to return a Route as you
showed, and keep the distinction between the ultimate target and the
next-hop route as distinct identities, where the LRF result populates a
Route header.

Other thoughts welcome.

Thanks,
Mike Hammer

> -----Original Message-----
> From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org]
On
> Behalf Of Alexander Mayrhofer
> Sent: Wednesday, February 24, 2010 11:28 AM
> To: speermint@ietf.org
> Subject: [Speermint] Clarification sought about LUF response data.
>=20
>=20
> As you probably know, DRINKS is working on a protocol that allows for
> provisioning of data which is then returned as Session Establishment
> Data in the chain of the LUF/LRF functions.
>=20
> We're currently discussion what type of data the LUF should return
(and
> therefore, what type/kind of data is used as input data for the LRF).
>=20
> The SPEERMINT documents are not consistent and entirely clear about
> this. I'm right now looking only at RFC5486 (which is the most
relevant
> document for terminology, obviously), and even that document
contradicts
> itself in the definition (Section 4.3.3):
>=20
>   "The Look-Up Function (LUF) determines for a given request the
target
>    domain to which the request should be routed.  An example of an LUF
>    is an ENUM [4] look-up or a SIP INVITE request to a SIP proxy
>    providing redirect responses for peers."
>=20
> The first sentence says "it returns a domain", while the examples in
the
> second sentence indicate that it would return a full AoR? I know that
a
> sip: URI does not need to contain a user part, but it seems the much
> more common case that ENUM or SIP redirect servers return sip: URIs
> including a user part.
>=20
> Looking at the ENUM and SIP redirect cases specifically, we think that
a
> typical useful LUF response would be as follows:
>=20
>   tel:+19195551234 -> LUF -> sip:+19195551234@voip.example.com
>=20
> rather than
>=20
>   tel:+19195551234 -> LUF -> sip:voip.example.com
>=20
> I think that the question is whether or not the LUF response
*replaces*
> the original URI, or rather *amends* it with the additional
information.
>=20
> It's also related to the question what data is fed into the LRF? Is
the
> only data fed into that function the response data from the LUF, or is
> it both the LUF response plus the original URI, eg.:
>=20
>  tel:+19195551234
>    plus               ----> LRF --->  sip:9195551234@192.168.2.12:123
>  sip:voip.example.com
>=20
> With the "domain only" LUF response alone, the LRF could just return a
> "generic" SF address that requires additional information to properly
> route the session:
>=20
> sip:voip.example.com  ----> LRF ----> sip:sbc@192.168.2.12:1234
>=20
> Therefore, it seems to us cleaner when the LUF returns a full AoR. It
> would still fit the definition of "determining the target domain", it
> just "copies" certain information from the input data to the output
data.
>=20
> Opinions and comments to clarify that?
>=20
> Alex
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint

From john.elwell@siemens-enterprise.com  Thu Feb 25 01:13:07 2010
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24EEF3A8676 for <speermint@core3.amsl.com>; Thu, 25 Feb 2010 01:13:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWg0W9I+gPY9 for <speermint@core3.amsl.com>; Thu, 25 Feb 2010 01:13:04 -0800 (PST)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 7D0293A866C for <speermint@ietf.org>; Thu, 25 Feb 2010 01:13:04 -0800 (PST)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1009058; Thu, 25 Feb 2010 10:15:12 +0100
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx11-mx (Server) with ESMTP id DC28F1EB82AB; Thu, 25 Feb 2010 10:15:12 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Thu, 25 Feb 2010 10:15:12 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "PFAUTZ, PENN L (ATTCORP)" <pp3129@att.com>, David Hancock <D.Hancock@CableLabs.com>, "speermint@ietf.org" <speermint@ietf.org>
Date: Thu, 25 Feb 2010 10:15:11 +0100
Thread-Topic: [Speermint] Should SIP Interconnect Guidelines recommendTransmission Loss?
Thread-Index: Acq1eoFba/pGrqW/TvC16ibYoYb92gAAQMCwAB+VMXA=
Message-ID: <A444A0F8084434499206E78C106220CABB8E7793@MCHP058A.global-ad.net>
References: <76AC5FEF83F1E64491446437EA81A61F7CD4B2B65A@srvxchg> <35FE871E2B085542A35726420E29DA6B036CCFB8@gaalpa1msgusr7a.ugd.att.com>
In-Reply-To: <35FE871E2B085542A35726420E29DA6B036CCFB8@gaalpa1msgusr7a.ugd.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Speermint] Should SIP Interconnect Guidelines	recommendTransmission Loss?
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 09:13:07 -0000

David,

I too am concerned about this. Implementations of the NNI (SIP proxies, B2B=
UAs, SBCs, etc.) will not in general be the media endpoints, so if we speci=
fy anything of this nature it will need to be made explicitly clear that it=
 applies to the media endpoints (e.g., user devices, gateways, media server=
s) and not to the signalling entities. In general a SIP service provider (c=
arrier or enterprise) is not in control of the media endpoints that use its=
 services and has no way of enforcing those media endpoints to comply with =
any NNI specification (and indeed has no way of telling those media endpoin=
ts whether a given medium for a given session is routed via an NNI). Theref=
ore whatever we specify for media endpoints, there is no way of guaranteein=
g that only compliant media endpoints will find themselves involved in a se=
ssion that crosses an NNI.

John

> -----Original Message-----
> From: speermint-bounces@ietf.org=20
> [mailto:speermint-bounces@ietf.org] On Behalf Of PFAUTZ, PENN=20
> L (ATTCORP)
> Sent: 24 February 2010 18:08
> To: David Hancock; speermint@ietf.org
> Subject: Re: [Speermint] Should SIP Interconnect Guidelines=20
> recommendTransmission Loss?
>=20
> David:
> I do not believe in IP interconnection we should be involved in
> manipulating loss. I see that as more a CPE or gateway function where
> conversion to analog is taking place. I see this has separate from the
> (IP) NNI.=20
>=20
> Penn Pfautz
> AT&T Access Management
> +1-732-420-4962
>=20
> -----Original Message-----
> From: speermint-bounces@ietf.org=20
> [mailto:speermint-bounces@ietf.org] On
> Behalf Of David Hancock
> Sent: Wednesday, February 24, 2010 12:55 PM
> To: speermint@ietf.org
> Subject: [Speermint] Should SIP Interconnect Guidelines
> recommendTransmission Loss?
>=20
> The current version of SPEERMINT
> draft-hancock-sip-interconnect-guidelines-02 places transmission loss
> out-of-scope. I'd like to propose that we move this to=20
> in-scope. I think
> this is important because the transmission loss inserted by=20
> both peering
> networks contributes to the end-to-end loss of the media connection.
> Improper end-to-end loss settings can affect voice quality (too
> loud/soft, annoying echo), and the ability of the connection to convey
> voice-band data such as DTMF digits.
>=20
> Does everyone agree this should be placed in-scope?=20
>=20
> If yes, what is the requirement? My thought is that we=20
> recommend support
> of TIA-912B at a minimum (and possibly ETSI ES 202 020 for=20
> international
> networks). There are other standards that affect the Overall Loudness
> Rating (OLR) of the media connection (e.g., TIA-470 specifies the
> SLR/RLR for analog handsets). Should we include these additional
> standards as well, or assume they get pulled in by TIA-912B=20
> (since 912B
> does informatively reference these other documents)? =20
>=20
> Thanks
> David
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> _______________________________________________
> Speermint mailing list
> Speermint@ietf.org
> https://www.ietf.org/mailman/listinfo/speermint
> =

From dschwartz@xconnect.net  Thu Feb 25 03:54:25 2010
Return-Path: <dschwartz@xconnect.net>
X-Original-To: speermint@core3.amsl.com
Delivered-To: speermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B8093A7B23 for <speermint@core3.amsl.com>; Thu, 25 Feb 2010 03:54:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.674
X-Spam-Level: 
X-Spam-Status: No, score=-1.674 tagged_above=-999 required=5 tests=[AWL=0.925,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3hkDeB8Kx8Ut for <speermint@core3.amsl.com>; Thu, 25 Feb 2010 03:54:24 -0800 (PST)
Received: from outlook.xconnect.net (outlook.xconnect.net [212.25.92.170]) by core3.amsl.com (Postfix) with ESMTP id 10E163A6F85 for <speermint@ietf.org>; Thu, 25 Feb 2010 03:54:23 -0800 (PST)
Received: from ISR-JLM-MAIL1.xconnect.co.il ([172.16.100.8]) by ISR-JLM-MAIL1.xconnect.co.il ([172.16.100.8]) with mapi; Thu, 25 Feb 2010 13:56:31 +0200
From: David Schwartz <dschwartz@xconnect.net>
To: Daryl Malas <D.Malas@cablelabs.com>, 'Alexander Mayrhofer' <alexander.mayrhofer@enum.at>, "speermint@ietf.org" <speermint@ietf.org>
Date: Thu, 25 Feb 2010 13:56:30 +0200
Thread-Topic: [Speermint] Clarification sought about LUF response data.
Thread-Index: Acq1bnF8ai3oVob8S+OaSQfWcI81/QADM1ZAACPqm+A=
Message-ID: <6EA53FAD386F9D46B97D49BFE148D51406A6BBEF@ISR-JLM-MAIL1.xconnect.co.il>
In-Reply-To: <114DAD31379DFA438C0A2E39B3B8AF5D01213F6663@srvxchg>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Speermint] Clarification sought about LUF response data.
X-BeenThere: speermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list for the speermint working group <speermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speermint>
List-Post: <mailto:speermint@ietf.org>
List-Help: <mailto:speermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speermint>, <mailto:speermint-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 11:54:25 -0000

So this issue seems to have plagued us since the inception of SPEERMINT and=
 unfortunately, I see no end in sight.

When attempting to connect to a remote entity using e.164 numbers over IP t=
he 3 (I left out identity mapping) basic questions are:
1. What is the identity of the remote side SP --> output can be an AOR
2. What is the remote side target --> output should be a target
3. How do I get there (LRF)

#1 takes the e.164 number and returns an identity (possibly an AOR)
#2 takes the identity/AOR and returns a target
#3 takes that target and figures out how to get there

Unfortunately, #2 and #3 have been grouped resulting in the confusion that =
prompted Alex's question regarding "the left side of the @ sign". It is per=
fectly legitimate to return a SPID in response to #1.

BTW - #2 may be done via some private mechanism (e.g. mapping SPID to targe=
t).

David

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Daryl Malas
Sent: Wednesday, February 24, 2010 8:12 PM
To: 'Alexander Mayrhofer'; speermint@ietf.org
Subject: Re: [Speermint] Clarification sought about LUF response data.

Alex,

The purpose of the definition is to say for a given request, +13035551212, =
the LUF determines the target domain, ssp.example.com; which, results in +1=
3035551212@ssp.example.com.  The LRF determines for ssp.example.com the app=
ropriate path to get there, for example:

$ORIGIN _sip._udp.ssp.example.com.
	IN   SRV  0   1   5060    big-sbe.ssp.example.com
	IN   SRV  1   1   5060    small-sbe.ssp.example.com
	IN   SRV  1   2   5060    old-big-sbe.ssp.example.com
big-sbe	A  192.168.5.5
small-sbe	A  192.168.4.5
old-big-sbe	A  192.168.100.5

Or, the LRF may return an egress route as described in draft-malas-enum-tru=
nk-sip-01, for example:=20

$ORIGIN 2.1.2.1.5.5.5.3.0.3.1.e164.arpa.
      NAPTR 10 100 "u" "E2U+sip"  "!^.*$!sip:\1;tgrp=3DTG-1;trunk-context=
=3Dssp2.example.com  @big-sbe.ssp.example.com;user=3Dphone!" .


Regards,

Daryl=20

-----Original Message-----
From: speermint-bounces@ietf.org [mailto:speermint-bounces@ietf.org] On Beh=
alf Of Alexander Mayrhofer
Sent: Wednesday, February 24, 2010 9:28 AM
To: speermint@ietf.org
Subject: [Speermint] Clarification sought about LUF response data.


As you probably know, DRINKS is working on a protocol that allows for provi=
sioning of data which is then returned as Session Establishment Data in the=
 chain of the LUF/LRF functions.

We're currently discussion what type of data the LUF should return (and the=
refore, what type/kind of data is used as input data for the LRF).

The SPEERMINT documents are not consistent and entirely clear about this. I=
'm right now looking only at RFC5486 (which is the most relevant document f=
or terminology, obviously), and even that document contradicts itself in th=
e definition (Section 4.3.3):

  "The Look-Up Function (LUF) determines for a given request the target
   domain to which the request should be routed.  An example of an LUF
   is an ENUM [4] look-up or a SIP INVITE request to a SIP proxy
   providing redirect responses for peers."

The first sentence says "it returns a domain", while the examples in the se=
cond sentence indicate that it would return a full AoR? I know that a
sip: URI does not need to contain a user part, but it seems the much more c=
ommon case that ENUM or SIP redirect servers return sip: URIs including a u=
ser part.

Looking at the ENUM and SIP redirect cases specifically, we think that a ty=
pical useful LUF response would be as follows:

  tel:+19195551234 -> LUF -> sip:+19195551234@voip.example.com

rather than

  tel:+19195551234 -> LUF -> sip:voip.example.com

I think that the question is whether or not the LUF response *replaces* the=
 original URI, or rather *amends* it with the additional information.

It's also related to the question what data is fed into the LRF? Is the onl=
y data fed into that function the response data from the LUF, or is it both=
 the LUF response plus the original URI, eg.:

 tel:+19195551234
   plus               ----> LRF --->  sip:9195551234@192.168.2.12:123
 sip:voip.example.com

With the "domain only" LUF response alone, the LRF could just return a "gen=
eric" SF address that requires additional information to properly route the=
 session:

sip:voip.example.com  ----> LRF ----> sip:sbc@192.168.2.12:1234

Therefore, it seems to us cleaner when the LUF returns a full AoR. It would=
 still fit the definition of "determining the target domain", it just "copi=
es" certain information from the input data to the output data.

Opinions and comments to clarify that?

Alex
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint
_______________________________________________
Speermint mailing list
Speermint@ietf.org
https://www.ietf.org/mailman/listinfo/speermint
