From gsalguei@cisco.com Wed May 29 22:47:53 2013 Return-Path: X-Original-To: insipid@ietfa.amsl.com Delivered-To: insipid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBF921F9433 for ; Wed, 29 May 2013 22:47:53 -0700 (PDT) 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVcEyvz6qovN for ; Wed, 29 May 2013 22:47:47 -0700 (PDT) Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 0FE1621F940D for ; Wed, 29 May 2013 22:47:41 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r4U5lfk6028598 for ; Thu, 30 May 2013 01:47:41 -0400 (EDT) Received: from rtp-gsalguei-8912.cisco.com (rtp-gsalguei-8912.cisco.com [10.116.132.51]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r4U5lZE6004870 for ; Thu, 30 May 2013 01:47:35 -0400 (EDT) From: Gonzalo Salgueiro Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 30 May 2013 01:47:35 -0400 References: To: "insipid@ietf.org" Message-Id: <77C10D27-B3C7-4FC7-B6AB-0DC3C6F19505@cisco.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) X-Mailer: Apple Mail (2.1503) Subject: [Insipid] Fwd: Nomcom 2013-14 Volunteering - 2nd Call X-BeenThere: insipid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Session-ID discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 May 2013 05:47:54 -0000 If you are eligible, please consider volunteering for this important = activity. Gonzalo Begin forwarded message: > From: "Mankin, Allison" > Subject: Nomcom 2013-14 Volunteering - 2nd Call > Date: May 29, 2013 5:04:51 PM EDT > To: "ietf-announce@ietf.org" > Cc: "" > Reply-To: >=20 > Hi, everyone, >=20 > Remember that I'm challenging the IETF to come up with 200 volunteers = for=20 > the upcoming nomcom. You can volunteer just by hitting Reply to this = email. >=20 > What are you waiting for?? The more volunteers we get, the better = chance we > have of choosing a random yet representative cross section of the IETF=20= > population. Respond to the 200-volunteer challenge and hit Reply = right now.=20 > (Well, much as I want you to do this, please look below at the posts = being > filled and be sure you are willing to forgo trying for any of them = this year). >=20 > The official information: > The IETF nominating committee (nomcom) process for 2013-14 is under = way. The=20 > IETF nomcom appoints folks to fill the open slots on the IAOC, the = IAB, > and the IESG. Ten voting members for the nomcom are selected in a = verifiably > random way from a pool of volunteers.=20 >=20 > The details of the selection and operation of the nomcom can be found=20= > in RFCs 3777, 5078, 5633, 5680, and 6859. Four of those RFCs (3777, = 5633,=20 > 5680 and 6859) comprise BCP 10. We will also reference RFC 3797. >=20 > Volunteers must have attended 3 of the past 5 IETF meetings. As = specified in > RFC 3777, that means three out of the five past meetings up to the = time this > email announcement goes out to start the solicitation of volunteers. = The five > meetings out of which you must have attended three are IETF 82, 83, = 84, 85, 86. >=20 > If you qualify, reply to this email and volunteer. =20 >=20 > The list of people and posts whose terms end with the March 2014 IETF > meeting, and thus the positions for which this nomcom is responsible, = are > IAOC: > Chris Griffiths >=20 > IAB: > Bernard Aboba > Marc Blanchet > Ross Callon > Eliot Lear > Hannes Tschofenig >=20 > IESG: > Barry Leiba (Applications) > Brian Haberman (Internet) > Benoit Claise (Operations and Management) > Gonzalo Camarillo (RAI) > Stewart Bryant (Routing) > Sean Turner (Security) > Martin Stiemerling (Transport) >=20 > The primary activity for this nomcom will begin in July 2013 and = should be > completed in January 2014. Being a nomcom member will require some = time > commitment - there will be interviews with candidates at meetings, = regularly > scheduled conference calls to ensure progress, collection and review = of=20 > requirements from the commitment, review of candidate questionnaires = and > of community feedback. A more detailed timetable for the nomcom tasks > will appear soon. >=20 > Please respond to this email before 11:59 pm EDT (UTC -4 hours)=20 > June 16, 2013. In the body include:=20 > 1. your Given Name as you enter it when you register for the IETF > 2. your Family Name as you enter it when you register for the IETF > 3. your current primary affilation (the information you enter into the = Company field) > 4. any/all email addresses you've used to register for IETF meetings=20= > 5. which email address you prefer=20 > 6. your phone number (for our use in confirming you if selected). >=20 > You should expect an email response from me within 3 business days = stating > whether or not you are qualified (and added to the list). If you = don't receive this > response, please re-send your email adding the tag "RESEND" to the = subject line. >=20 > Participating in the IETF nomcom is a meaningful and fun way to = contribute to the IETF. =20 > Please help us meet the 200-volunteer challenge by hitting Reply to = this message today. =20 >=20 > Allison=20 >=20 > Allison Mankin > Nomcom Chair 2013-2014 >=20 >=20 From internet-drafts@ietf.org Thu May 30 23:07:45 2013 Return-Path: X-Original-To: insipid@ietfa.amsl.com Delivered-To: insipid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B9D21F8D31; Thu, 30 May 2013 23:07:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.533 X-Spam-Level: X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YWrideFaMTpQ; Thu, 30 May 2013 23:07:43 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8C821F871D; Thu, 30 May 2013 23:07:24 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.50 Message-ID: <20130531060724.6960.89722.idtracker@ietfa.amsl.com> Date: Thu, 30 May 2013 23:07:24 -0700 Cc: insipid@ietf.org Subject: [Insipid] I-D Action: draft-ietf-insipid-session-id-reqts-06.txt X-BeenThere: insipid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Session-ID discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 06:07:45 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the INtermediary-safe SIP session ID Working = Group of the IETF. Title : Requirements for an End-to-End Session Identification in= IP-Based Multimedia Communication Networks Author(s) : Paul E. Jones Gonzalo Salgueiro James Polk Laura Liess Hadriel Kaplan Filename : draft-ietf-insipid-session-id-reqts-06.txt Pages : 12 Date : 2013-05-30 Abstract: This document specifies the requirements for an end-to-end session identifier in IP-based multimedia communication networks. This identifier would enable endpoints, intermediate devices, and management and monitoring systems to identify a session end-to-end across multiple SIP devices, hops, and administrative domains. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-insipid-session-id-reqts There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-insipid-session-id-reqts-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-insipid-session-id-reqts-06 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From paulej@packetizer.com Thu May 30 23:17:55 2013 Return-Path: X-Original-To: insipid@ietfa.amsl.com Delivered-To: insipid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 593DB21F8E9A for ; Thu, 30 May 2013 23:17:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.504 X-Spam-Level: X-Spam-Status: No, score=-2.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K8Xydh9L5G5l for ; Thu, 30 May 2013 23:17:50 -0700 (PDT) Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 29A6121F8DE4 for ; Thu, 30 May 2013 23:17:50 -0700 (PDT) Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r4V6HnxQ030992 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 31 May 2013 02:17:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1369981069; bh=k/n4Np+fh5ELk1qDPCXtTp7cOjS0X7pNPMcn337VZR8=; h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=iX2hByFU5X25+9q7+DfsXA66/TWw3p4tHwU0yuYDQLgohZr+1iZZb34V3SAhgyUKB etHuogmw8aPekpE7dUEYT3Is2Ld9k3kgI2RtyUBZ+U7v6JW9XuK7c4uvbnZM566IjM th1/dqKVrPF9U7LGh1XpQaaixIoeYcBAV0qM3Mfc= From: "Paul E. Jones" To: Date: Fri, 31 May 2013 02:17:59 -0400 Message-ID: <02ab01ce5dc6$99720fa0$cc562ee0$@packetizer.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac5dxZGUZsnLUml5TGWeVD2BQP0kyA== Content-Language: en-us Subject: [Insipid] Comments on draft-ietf-insipid-session-id-reqts-06 X-BeenThere: insipid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Session-ID discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 06:17:55 -0000 Folks, I posted a revision to the requirements document. This includes new text that was provided by Robert that expands on what a Session ID identifies. We decided to integrate the new text within the terminology section and to create a few sub-sections. The former text that described a communication session is still there. However, it's not positioned to try to explain a Session ID, but to expand on what constitutes a communication session. We struggled with making any changes to that text. We felt it was useful to have that text, but we appreciate that others might not agree. So, taking a fresh look at the terminology section, do you feel this explains a what a session ID is and what a communication session is? Is it missing something? Over-stating anything? I do feel it's a bit long, but we did not want to remove anything out of concern that we weaken the explanation. Feedback is much appreciated. Paul From pkyzivat@alum.mit.edu Fri May 31 07:25:36 2013 Return-Path: X-Original-To: insipid@ietfa.amsl.com Delivered-To: insipid@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C051621F9928 for ; Fri, 31 May 2013 07:25:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.252 X-Spam-Level: X-Spam-Status: No, score=-0.252 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gj-wtvN47Ktf for ; Fri, 31 May 2013 07:25:32 -0700 (PDT) Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id D69A421F991F for ; Fri, 31 May 2013 07:25:31 -0700 (PDT) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta08.westchester.pa.mail.comcast.net with comcast id ibkx1l0010bG4ec58eRXTM; Fri, 31 May 2013 14:25:31 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta03.westchester.pa.mail.comcast.net with comcast id ieRW1l0173ZTu2S3PeRWsz; Fri, 31 May 2013 14:25:31 +0000 Message-ID: <51A8B2D9.7030104@alum.mit.edu> Date: Fri, 31 May 2013 10:25:29 -0400 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: insipid@ietf.org References: <02ab01ce5dc6$99720fa0$cc562ee0$@packetizer.com> In-Reply-To: <02ab01ce5dc6$99720fa0$cc562ee0$@packetizer.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1370010331; bh=DjKYkujbgjToa+FO7yq2MFyUuW7Uxu07zlS5Kpy/iLE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=VsEyn2kJ1tk/AJOdZqa08Twx19qK/sMQfHIZ6FDTt8w1jGJMUgZ2ckgTvU6CVx+wO uDgy4k8IGjVNtcosmWMV4ClsRXkbRPQT4ufFUzsJDaYqqPWwb6ZvD88chbxMyaSiRI qV02KXjOP0SttKaBKtNqw5s8YLcEf3AybF8ohKNsYcYeCv9CVMAccX0ifnnZGo61fx PwMWDaZ2YeK6uvUkxktl+SwImK389GVHkAReJ4scEljqQ2cEEBk60hrFQCVYrpJSxn Vup5o8V49HhJAFlUlSK6kJiUTMo9lr3h6AucjxwqsGdU4p4fxu5lI3fl7AyroeDL40 N2sCr5gaP+GeQ== Subject: Re: [Insipid] Comments on draft-ietf-insipid-session-id-reqts-06 X-BeenThere: insipid@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIP Session-ID discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 14:25:36 -0000 This is a big improvement! Thanks, Paul On 5/31/13 2:17 AM, Paul E. Jones wrote: > Folks, > > I posted a revision to the requirements document. This includes new text > that was provided by Robert that expands on what a Session ID identifies. > > We decided to integrate the new text within the terminology section and to > create a few sub-sections. The former text that described a communication > session is still there. However, it's not positioned to try to explain a > Session ID, but to expand on what constitutes a communication session. We > struggled with making any changes to that text. We felt it was useful to > have that text, but we appreciate that others might not agree. > > So, taking a fresh look at the terminology section, do you feel this > explains a what a session ID is and what a communication session is? Is it > missing something? Over-stating anything? I do feel it's a bit long, but > we did not want to remove anything out of concern that we weaken the > explanation. > > Feedback is much appreciated. > > Paul > > > _______________________________________________ > insipid mailing list > insipid@ietf.org > https://www.ietf.org/mailman/listinfo/insipid >