From tsvwg-bounces@ietf.org Sun Jun 1 13:30:48 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9798128C624; Sun, 1 Jun 2008 13:30:48 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5727C28C4F8 for ; Sun, 1 Jun 2008 13:29:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.989 X-Spam-Level: X-Spam-Status: No, score=-5.989 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 N5-oryJ1dOH8 for ; Sun, 1 Jun 2008 13:29:14 -0700 (PDT) Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id BF22F28CE22 for ; Sun, 1 Jun 2008 10:29:31 -0700 (PDT) Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 1E9D420062; Sun, 1 Jun 2008 19:29:31 +0200 (CEST) X-AuditID: c1b4fb3c-aa894bb00000193b-17-4842dc7a5cb4 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id EB0EC20047; Sun, 1 Jun 2008 19:29:30 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun, 1 Jun 2008 19:29:30 +0200 Received: from [127.0.0.1] ([153.88.44.63]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun, 1 Jun 2008 19:29:30 +0200 Message-ID: <4842DC74.7000105@ericsson.com> Date: Sun, 01 Jun 2008 19:29:24 +0200 From: Magnus Westerlund User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Adrian Farrel References: <001401c8c30b$ecf847d0$0200a8c0@your029b8cecfe> In-Reply-To: <001401c8c30b$ecf847d0$0200a8c0@your029b8cecfe> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 01 Jun 2008 17:29:30.0418 (UTC) FILETIME=[0C8C0120:01C8C40D] X-Brightmail-Tracker: AAAAAA== Cc: George Swallow , jari.arkko@piuha.net, Chris Newman , tsvwg Subject: Re: [Tsvwg] Fw: New Version Notification for draft-ietf-tsvwg-rsvp-user-error-spec-08 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org TSVWG If you have any opinions on this change please express this quickly. I will give everyone a week to consider these changes. Cheers Magnus Adrian Farrel skrev: > Hi Chris, > > The new revision of this I-D is intended to address your concerns. > > I have moved over to UTF-8 with references and a recommendation to limit > to US-ASCII. > > I have also commented on how to handle UTF-8 in an ASCII system, and > briefly noted the security risk of character strings in a protocol. > > Having discussed language codes, we have decided not to include them. > The only reason for not including them is that no-one in the WG > expressed any support. > > Let me know what you think. Hoping you will clear. > > Cheers, > Adrian > > ----- Original Message ----- From: "IETF I-D Submission Tool" > > To: > Cc: > Sent: Saturday, May 31, 2008 11:44 AM > Subject: New Version Notification for > draft-ietf-tsvwg-rsvp-user-error-spec-08 > > >> >> A new version of I-D, draft-ietf-tsvwg-rsvp-user-error-spec-08.txt has >> been successfuly submitted by Adrian Farrel and posted to the IETF >> repository. >> >> Filename: draft-ietf-tsvwg-rsvp-user-error-spec >> Revision: 08 >> Title: User-Defined Errors for RSVP >> Creation_date: 2008-05-31 >> WG ID: tsvwg >> Number_of_pages: 9 >> >> Abstract: >> The Resource ReserVation Protocol (RSVP) defines an ERROR_SPEC object >> for communicating errors. That object has a defined format that >> permits the definition of 256 error codes. As RSVP has been >> developed and extended, the convention has been to be conservative in >> defining new error codes. Further, no provision for user-defined >> errors exists in RSVP. >> >> This document defines a USER_ERROR_SPEC to be used in addition to the >> ERROR_SPEC to carry additional user information related to errors. >> >> >> >> The IETF Secretariat. >> >> >> > > > -- Magnus Westerlund IETF Transport Area Director & TSVWG Chair ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Färögatan 6 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From tsvwg-bounces@ietf.org Wed Jun 11 21:36:22 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA1313A684F; Wed, 11 Jun 2008 21:36:21 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FF473A689F for ; Wed, 11 Jun 2008 21:36:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.595 X-Spam-Level: X-Spam-Status: No, score=0.595 tagged_above=-999 required=5 tests=[AWL=-0.803, BAYES_50=0.001, HTML_MESSAGE=0.001, WEIRD_QUOTING=1.396] 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 HWimBnwWRo0X for ; Wed, 11 Jun 2008 21:36:20 -0700 (PDT) Received: from n2a.bullet.in.yahoo.com (n2a.bullet.in.yahoo.com [202.43.219.19]) by core3.amsl.com (Postfix) with SMTP id 8664A3A67B5 for ; Wed, 11 Jun 2008 21:36:19 -0700 (PDT) Received: from [202.86.4.170] by n2.bullet.in.yahoo.com with NNFMP; 12 Jun 2008 04:36:45 -0000 Received: from [203.104.18.50] by t1.bullet.in.yahoo.com with NNFMP; 12 Jun 2008 04:36:45 -0000 Received: from [127.0.0.1] by omp111.mail.in2.yahoo.com with NNFMP; 12 Jun 2008 04:36:45 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 871554.56304.bm@omp111.mail.in2.yahoo.com Received: (qmail 54308 invoked by uid 60001); 12 Jun 2008 04:36:45 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=E8p6rUP53kuSTJs7jZ/i9VHHrz6DhxQWBE1N+Skr0BCltlvhThF0Pk+hUWUk0ERsHmjNpWWDSlZYuVFNwT/112kT/dLN2k3mqbFX0WKk/2kf94XsGTLjLY1VGUX6tuxhFFQy6P6QBU1Fx8Bq4qQq7QQ83eaxLmeASPBfHy+lTTM=; Received: from [125.21.164.251] by web94607.mail.in2.yahoo.com via HTTP; Thu, 12 Jun 2008 10:06:45 IST X-Mailer: YahooMailRC/975.42 YahooMailWebService/0.7.199 Date: Thu, 12 Jun 2008 10:06:45 +0530 (IST) From: Ash Kat To: tsvwg@ietf.org, sigtran@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-208209257-1213245405=:54277" Message-ID: <780120.54277.qm@web94607.mail.in2.yahoo.com> Subject: [Tsvwg] [SCTP] a small correction in RFC 4960 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org --0-208209257-1213245405=:54277 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello:=0A'Path.Max.Retrans' parmeters specifies the maximum number of retra= nsmission on a path before that path is marked down.=0ASection 8.3 of RFC s= ays:=0A=C2=A0=C2=A0 When the value of this counter ""reaches"" the protocol= parameter=0A=C2=A0=C2=A0 'Path.Max.Retrans', the endpoint should mark the = corresponding=0A=C2=A0=C2=A0 destination address as inactive if it is not s= o marked, and may also=0A=C2=A0=C2=A0 optionally report to the upper layer = the change of reachability of=0A=C2=A0=C2=A0 this destination address.=0ATh= is will make the Heartbeat to=C2=A0be re-transmitted one count less=C2=A0th= en 'Path.Max.Retrans'=0AThis is correct in Section 8.2 which says:=0A=C2=A0= =C2=A0 When the value in the error counter ""exceeds"" the protocol paramet= er=0A=C2=A0=C2=A0 'Path.Max.Retrans' of that destination address, the endpo= int should=0A=C2=A0=C2=A0 mark the destination transport address as inactiv= e, and a=0A=C2=A0=C2=A0 notification SHOULD be sent to the upper layer.=0AS= o Section 8.3 should=C2=A0be modified and a path should be marked down=C2= =A0when error count exceeds 'Path.Max.Retrans'.=0ARegards,=0AAshwani Kathur= ia=0A=0A=0A From Chandigarh to Chennai - find friends all over India. = Go to http://in.promos.yahoo.com/groups/citygroups/ --0-208209257-1213245405=:54277 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello:
=0A
 
=0A
'P= ath.Max.Retrans' parmeters specifies the maximum number of retransmission o= n a path before that path is marked down.
=0A
 
=0A
= Section 8.3 of RFC says:
=0A
   When the value of this c= ounter ""reaches"" the protocol parameter
   'Path.Max.Retrans= ', the endpoint should mark the corresponding
   destination a= ddress as inactive if it is not so marked, and may also
   opt= ionally report to the upper layer the change of reachability of
 &n= bsp; this destination address.
=0A
 
=0A
This will m= ake the Heartbeat to be re-transmitted one count less then 'Path.= Max.Retrans'
=0A
 
=0A
This is correct in Section 8.= 2 which says:
=0A
   When the value in the error counter= ""exceeds"" the protocol parameter
   'Path.Max.Retrans' of t= hat destination address, the endpoint should
   mark the desti= nation transport address as inactive, and a
   notification SH= OULD be sent to the upper layer.
=0A
 
=0A
So Sectio= n 8.3 should be modified and a path should be marked down when er= ror count exceeds 'Path.Max.Retrans'.
=0A
 
=0A
Rega= rds,
=0A
Ashwani Kathuria

=0A=0A=0A Bring your gang together. Do your thing. Find= your favourite Yahoo! Group. --0-208209257-1213245405=:54277-- From tsvwg-bounces@ietf.org Thu Jun 12 00:44:37 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0E463A68C9; Thu, 12 Jun 2008 00:44:37 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D40893A697D; Thu, 12 Jun 2008 00:44:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.961 X-Spam-Level: *** X-Spam-Status: No, score=3.961 tagged_above=-999 required=5 tests=[AWL=0.527, BAYES_00=-2.599, HOST_EQ_DIP_TDIAL=2.144, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, WEIRD_QUOTING=1.396] 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 yqB+XerOkmvt; Thu, 12 Jun 2008 00:44:35 -0700 (PDT) Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 44E343A6819; Thu, 12 Jun 2008 00:44:35 -0700 (PDT) Received: from [192.168.1.199] (p508FD701.dip.t-dialin.net [80.143.215.1]) by mail-n.franken.de (Postfix) with ESMTP id 0FC231C0C0BCA; Thu, 12 Jun 2008 09:44:59 +0200 (CEST) Message-Id: From: =?ISO-8859-1?Q?Michael_T=FCxen?= To: Ash Kat In-Reply-To: <780120.54277.qm@web94607.mail.in2.yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Thu, 12 Jun 2008 09:44:59 +0200 References: <780120.54277.qm@web94607.mail.in2.yahoo.com> X-Mailer: Apple Mail (2.924) Cc: sigtran@ietf.org, tsvwg@ietf.org Subject: Re: [Tsvwg] [SCTP] a small correction in RFC 4960 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org Hi Ash, yes, that is a (at least by me) known issue... This comes up, when you dimension your parameters to fullfil a given path error detection time... I'm not sure if we should start again an errata ID... Best regards Michael On Jun 12, 2008, at 6:36 AM, Ash Kat wrote: > Hello: > > 'Path.Max.Retrans' parmeters specifies the maximum number of > retransmission on a path before that path is marked down. > > Section 8.3 of RFC says: > When the value of this counter ""reaches"" the protocol parameter > 'Path.Max.Retrans', the endpoint should mark the corresponding > destination address as inactive if it is not so marked, and may > also > optionally report to the upper layer the change of reachability of > this destination address. > > This will make the Heartbeat to be re-transmitted one count less > then 'Path.Max.Retrans' > > This is correct in Section 8.2 which says: > When the value in the error counter ""exceeds"" the protocol > parameter > 'Path.Max.Retrans' of that destination address, the endpoint should > mark the destination transport address as inactive, and a > notification SHOULD be sent to the upper layer. > > So Section 8.3 should be modified and a path should be marked down > when error count exceeds 'Path.Max.Retrans'. > > Regards, > Ashwani Kathuria > > Bring your gang together. Do your thing. Find your favourite Yahoo! > Group. From tsvwg-bounces@ietf.org Thu Jun 12 01:25:02 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 153143A69A2; Thu, 12 Jun 2008 01:25:02 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCB4E3A69F0; Thu, 12 Jun 2008 01:25:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.629 X-Spam-Level: X-Spam-Status: No, score=-5.629 tagged_above=-999 required=5 tests=[AWL=-0.726, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, WEIRD_QUOTING=1.396] 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 GeZ-h6gN-Nzu; Thu, 12 Jun 2008 01:24:58 -0700 (PDT) Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id C03923A69A2; Thu, 12 Jun 2008 01:24:56 -0700 (PDT) Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m5C8P1OA017878; Thu, 12 Jun 2008 11:25:21 +0300 Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Jun 2008 11:25:20 +0300 Received: from net-119.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Jun 2008 11:25:19 +0300 Message-Id: From: Lars Eggert To: =?ISO-8859-1?Q?ext_Michael_T=FCxen?= In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v924) Date: Thu, 12 Jun 2008 10:25:11 +0200 References: <780120.54277.qm@web94607.mail.in2.yahoo.com> X-Mailer: Apple Mail (2.924) X-OriginalArrivalTime: 12 Jun 2008 08:25:20.0538 (UTC) FILETIME=[DA3EEFA0:01C8CC65] X-Nokia-AV: Clean Cc: sigtran@ietf.org, tsvwg@ietf.org Subject: Re: [Tsvwg] [SCTP] a small correction in RFC 4960 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org Submit it as an errata to the RFC Editor for now. Lars On 2008-6-12, at 9:44, ext Michael T=FCxen wrote: > Hi Ash, > > yes, that is a (at least by me) known issue... This comes up, when you > dimension your parameters to fullfil a given path error detection =20 > time... > > I'm not sure if we should start again an errata ID... > > Best regards > Michael > > On Jun 12, 2008, at 6:36 AM, Ash Kat wrote: > >> Hello: >> >> 'Path.Max.Retrans' parmeters specifies the maximum number of =20 >> retransmission on a path before that path is marked down. >> >> Section 8.3 of RFC says: >> When the value of this counter ""reaches"" the protocol parameter >> 'Path.Max.Retrans', the endpoint should mark the corresponding >> destination address as inactive if it is not so marked, and may =20 >> also >> optionally report to the upper layer the change of reachability of >> this destination address. >> >> This will make the Heartbeat to be re-transmitted one count less =20 >> then 'Path.Max.Retrans' >> >> This is correct in Section 8.2 which says: >> When the value in the error counter ""exceeds"" the protocol =20 >> parameter >> 'Path.Max.Retrans' of that destination address, the endpoint should >> mark the destination transport address as inactive, and a >> notification SHOULD be sent to the upper layer. >> >> So Section 8.3 should be modified and a path should be marked down =20= >> when error count exceeds 'Path.Max.Retrans'. >> >> Regards, >> Ashwani Kathuria >> >> Bring your gang together. Do your thing. Find your favourite Yahoo! =20= >> Group. > From tsvwg-bounces@ietf.org Thu Jun 12 05:10:42 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33ABB3A6A46; Thu, 12 Jun 2008 05:10:42 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7840E3A6A46 for ; Thu, 12 Jun 2008 05:10:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 xPqHzf+aEGiP for ; Thu, 12 Jun 2008 05:10:39 -0700 (PDT) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by core3.amsl.com (Postfix) with ESMTP id 75F253A6892 for ; Thu, 12 Jun 2008 05:10:39 -0700 (PDT) Received: by py-out-1112.google.com with SMTP id x19so1298402pyg.24 for ; Thu, 12 Jun 2008 05:11:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=Tq0Hb6mnIHUZFDonB5VR2GNzCZpmboU9VihR4hJt1/c=; b=ZoxbMLMeDPX3ASLT/04OEJS6a+2GeME0M4igZi3H6QDEzUjJq2mtXJg9hhi/nCfYM1 xa+S3IXV7CvDd3D9hkqvTF/gVd+9h4eVGYYqyKll9UH6dpsQf67hoP+0vdHRWKx5c7ye lcK5lV8qR3DfH/IrxIVKFiiUZeqzYgr/Mwcsc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=EDn1Np/Im0zdpJPtf7sc/Ub5EVpzujxzH5Kq4CVXAA8A/N3OKucTgFeaM4iV4+pNYw O4cf0UEDsiJUv+gWI2eG/VYCAfw4wulnZ4aK8RlJXLM8QtqMwyH1nM/cPUr8XecOCfPg oJtJ4/LsEKBlTbndn0afHH9/aJamLcUxPEveY= Received: by 10.142.142.14 with SMTP id p14mr449708wfd.315.1213272667225; Thu, 12 Jun 2008 05:11:07 -0700 (PDT) Received: by 10.142.242.1 with HTTP; Thu, 12 Jun 2008 05:11:07 -0700 (PDT) Message-ID: Date: Thu, 12 Jun 2008 17:41:07 +0530 From: "Bharati Bhole" To: tsvwg@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [Tsvwg] Registering a socket for neighbour updates callback X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org Could anyone please tell me, how to register a socket to get neighbour table update call back. For example, one can get route table update, by creating a netlink socket and registering it in "nl_groups" and then setting function pointer "sk_data_ready" from sk. This invoks the function pointer by "sk_data_ready" whenever route table is modified. Could somebody please tell the procedure to get the neighbour table callbacks . Regards, Bharati. From tsvwg-bounces@ietf.org Thu Jun 12 09:41:30 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E91628C11A; Thu, 12 Jun 2008 09:41:30 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3956928C102 for ; Thu, 12 Jun 2008 09:41:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.599 X-Spam-Level: X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 8tDQ8fqmRx4b for ; Thu, 12 Jun 2008 09:41:28 -0700 (PDT) Received: from g5t0008.atlanta.hp.com (g5t0008.atlanta.hp.com [15.192.0.45]) by core3.amsl.com (Postfix) with ESMTP id 24B263A6A04 for ; Thu, 12 Jun 2008 09:41:28 -0700 (PDT) Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.11.136.114]) by g5t0008.atlanta.hp.com (Postfix) with ESMTP id 6E9662430F; Thu, 12 Jun 2008 16:41:56 +0000 (UTC) Received: from [192.168.98.100] (squirrel.fc.hp.com [15.11.146.57]) by smtp2.fc.hp.com (Postfix) with ESMTP id E467D277444; Thu, 12 Jun 2008 16:38:06 +0000 (UTC) Message-ID: <485151D2.9000701@hp.com> Date: Thu, 12 Jun 2008 12:41:54 -0400 From: Vlad Yasevich User-Agent: Thunderbird 2.0.0.4 (X11/20070604) MIME-Version: 1.0 To: Bharati Bhole References: In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: tsvwg@ietf.org Subject: Re: [Tsvwg] Registering a socket for neighbour updates callback X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org Bharati Bhole wrote: > Could anyone please tell me, how to register a socket to get neighbour > table update call back. > > For example, one can get route table update, by creating a netlink > socket and registering it in "nl_groups" and then setting function > pointer "sk_data_ready" from sk. > This invoks the function pointer by "sk_data_ready" whenever route > table is modified. > > Could somebody please tell the procedure to get the neighbour table callbacks . > > Regards, > Bharati. > This is a wrong mailing list for this question. It sounds like you are using linux and should direct these questions to linux-net@vger.kernel.org or netdev@vger.kernel.org -vlad From tsvwg-bounces@ietf.org Thu Jun 12 10:02:20 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4EFE3A6823; Thu, 12 Jun 2008 10:02:20 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 200CA3A6823; Thu, 12 Jun 2008 10:02:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.247 X-Spam-Level: X-Spam-Status: No, score=-1.247 tagged_above=-999 required=5 tests=[AWL=1.352, 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 xqME1SvhbzSp; Thu, 12 Jun 2008 10:02:18 -0700 (PDT) Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id E32A53A67AB; Thu, 12 Jun 2008 10:02:13 -0700 (PDT) Received: from wilbur.pigworks.openss7.net (IDENT:97/J63opGlkLpOj5Y6ruB36b1H5ktCL8@ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.13.8/8.13.8/Debian-3) with ESMTP id m5C6l2VG015695; Thu, 12 Jun 2008 00:47:02 -0600 Received: from wilbur.pigworks.openss7.net (IDENT:uVxrGKvmrLTLZu7vaDlyN5F/Usujne5b@localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Debian-3) with ESMTP id m5C6l29p021249; Thu, 12 Jun 2008 00:47:02 -0600 Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.13.8/8.13.8/Submit) id m5C6l1Db021247; Thu, 12 Jun 2008 00:47:01 -0600 Date: Thu, 12 Jun 2008 00:47:01 -0600 From: "Brian F. G. Bidulock" To: Ash Kat Message-ID: <20080612064701.GA20741@openss7.org> Mail-Followup-To: Ash Kat , tsvwg@ietf.org, sigtran@ietf.org References: <780120.54277.qm@web94607.mail.in2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <780120.54277.qm@web94607.mail.in2.yahoo.com> Organization: http://www.openss7.org/ Dsn-Notification-To: X-Spam-To: User-Agent: Mutt/1.5.13 (2006-08-11) Cc: sigtran@ietf.org, tsvwg@ietf.org Subject: Re: [Tsvwg] [SCTP] a small correction in RFC 4960 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: bidulock@openss7.org List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org Ash, Yes, I agree. This looks worth submitting to the RFC Editor as an Errata to RFC 4960. --brian Ash Kat wrote: (Thu, 12 Jun 2008 10:06:45) > > So Section 8.3 should be modified and a path should be marked > down when error count exceeds 'Path.Max.Retrans'. > -- Brian F. G. Bidulock bidulock@openss7.org http://www.openss7.org/ From tsvwg-bounces@ietf.org Thu Jun 12 11:30:26 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B0F213A6B09; Thu, 12 Jun 2008 11:30:26 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D1273A6B0D; Thu, 12 Jun 2008 11:30:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.785 X-Spam-Level: *** X-Spam-Status: No, score=3.785 tagged_above=-999 required=5 tests=[AWL=0.351, BAYES_00=-2.599, HOST_EQ_DIP_TDIAL=2.144, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, WEIRD_QUOTING=1.396] 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 K72zVfUXPXo5; Thu, 12 Jun 2008 11:30:24 -0700 (PDT) Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by core3.amsl.com (Postfix) with ESMTP id 9FA6D3A6B02; Thu, 12 Jun 2008 11:30:23 -0700 (PDT) Received: from [192.168.1.199] (p508FD233.dip.t-dialin.net [80.143.210.51]) by mail-n.franken.de (Postfix) with ESMTP id 795E41C0C0BCA; Thu, 12 Jun 2008 20:30:49 +0200 (CEST) Message-Id: From: =?ISO-8859-1?Q?Michael_T=FCxen?= To: Lars Eggert In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v924) Date: Thu, 12 Jun 2008 20:30:48 +0200 References: <780120.54277.qm@web94607.mail.in2.yahoo.com> X-Mailer: Apple Mail (2.924) Cc: sigtran@ietf.org, tsvwg@ietf.org Subject: Re: [Tsvwg] [SCTP] a small correction in RFC 4960 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org Hi Lars, I have submitted an errata. The correct text should say in section 8.3: When the value of this counter exceeds the protocol parameter 'Path.Max.Retrans', the endpoint should mark the corresponding destination address as inactive if it is not so marked, and may also optionally report to the upper layer the change of reachability of this destination address. Best regards Michael On Jun 12, 2008, at 10:25 AM, Lars Eggert wrote: > Submit it as an errata to the RFC Editor for now. > > Lars > > On 2008-6-12, at 9:44, ext Michael T=FCxen wrote: > >> Hi Ash, >> >> yes, that is a (at least by me) known issue... This comes up, when =20= >> you >> dimension your parameters to fullfil a given path error detection =20 >> time... >> >> I'm not sure if we should start again an errata ID... >> >> Best regards >> Michael >> >> On Jun 12, 2008, at 6:36 AM, Ash Kat wrote: >> >>> Hello: >>> >>> 'Path.Max.Retrans' parmeters specifies the maximum number of =20 >>> retransmission on a path before that path is marked down. >>> >>> Section 8.3 of RFC says: >>> When the value of this counter ""reaches"" the protocol parameter >>> 'Path.Max.Retrans', the endpoint should mark the corresponding >>> destination address as inactive if it is not so marked, and may =20 >>> also >>> optionally report to the upper layer the change of reachability of >>> this destination address. >>> >>> This will make the Heartbeat to be re-transmitted one count less =20 >>> then 'Path.Max.Retrans' >>> >>> This is correct in Section 8.2 which says: >>> When the value in the error counter ""exceeds"" the protocol =20 >>> parameter >>> 'Path.Max.Retrans' of that destination address, the endpoint should >>> mark the destination transport address as inactive, and a >>> notification SHOULD be sent to the upper layer. >>> >>> So Section 8.3 should be modified and a path should be marked down =20= >>> when error count exceeds 'Path.Max.Retrans'. >>> >>> Regards, >>> Ashwani Kathuria >>> >>> Bring your gang together. Do your thing. Find your favourite =20 >>> Yahoo! Group. >> > > From tsvwg-bounces@ietf.org Fri Jun 13 07:45:39 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91D903A69A1; Fri, 13 Jun 2008 07:45:38 -0700 (PDT) X-Original-To: tsvwg@ietf.org Delivered-To: tsvwg@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 97A183A697E; Fri, 13 Jun 2008 07:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20080613144503.97A183A697E@core3.amsl.com> Date: Fri, 13 Jun 2008 07:45:01 -0700 (PDT) Cc: tsvwg@ietf.org Subject: [Tsvwg] I-D Action:draft-ietf-tsvwg-udp-guidelines-08.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : Guidelines for Application Designers on Using Unicast UDP Author(s) : L. Eggert, G. Fairhurst Filename : draft-ietf-tsvwg-udp-guidelines-08.txt Pages : 27 Date : 2008-06-13 The User Datagram Protocol (UDP) provides a minimal, message-passing transport that has no inherent congestion control mechanisms. Because congestion control is critical to the stable operation of the Internet, applications and upper-layer protocols that choose to use UDP as an Internet transport must employ mechanisms to prevent congestion collapse and establish some degree of fairness with concurrent traffic. This document provides guidelines on the use of UDP for the designers of unicast applications and upper-layer protocols. Congestion control guidelines are a primary focus, but the document also provides guidance on other topics, including message sizes, reliability, checksums and middlebox traversal. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-udp-guidelines-08.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-tsvwg-udp-guidelines-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2008-06-13073746.I-D@ietf.org> --NextPart-- From tsvwg-bounces@ietf.org Fri Jun 13 07:53:06 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D50203A6982; Fri, 13 Jun 2008 07:53:06 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E008E3A6982 for ; Fri, 13 Jun 2008 07:53:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.471 X-Spam-Level: X-Spam-Status: No, score=-6.471 tagged_above=-999 required=5 tests=[AWL=0.128, 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 ib2yPzq63Ojx for ; Fri, 13 Jun 2008 07:53:05 -0700 (PDT) Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 9D9733A6829 for ; Fri, 13 Jun 2008 07:53:04 -0700 (PDT) Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id m5DErOcG030302 for ; Fri, 13 Jun 2008 17:53:34 +0300 Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Jun 2008 17:52:14 +0300 Received: from net-92.nrpn.net ([10.241.184.208]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Jun 2008 17:52:13 +0300 Message-Id: <3B53168A-3315-4DC8-B69F-390EF39DD7B8@nokia.com> From: Lars Eggert To: tsvwg WG In-Reply-To: <20080613144503.97A183A697E@core3.amsl.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Fri, 13 Jun 2008 17:52:08 +0300 References: <20080613144503.97A183A697E@core3.amsl.com> X-Mailer: Apple Mail (2.924) X-OriginalArrivalTime: 13 Jun 2008 14:52:14.0226 (UTC) FILETIME=[11185F20:01C8CD65] X-Nokia-AV: Clean Subject: Re: [Tsvwg] I-D Action:draft-ietf-tsvwg-udp-guidelines-08.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org This revision fixes some language issues found by Alfred. No technical changes. Lars On 2008-6-13, at 17:45, ext Internet-Drafts@ietf.org wrote: > Title : Guidelines for Application Designers on Using > Unicast UDP > Author(s) : L. Eggert, G. Fairhurst > Filename : draft-ietf-tsvwg-udp-guidelines-08.txt From tsvwg-bounces@ietf.org Wed Jun 18 13:27:02 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E181628C1E1; Wed, 18 Jun 2008 13:27:02 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 527E928C1E1 for ; Wed, 18 Jun 2008 13:27:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.478 X-Spam-Level: X-Spam-Status: No, score=-6.478 tagged_above=-999 required=5 tests=[AWL=0.121, 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 1UGI5Ffu9Kzi for ; Wed, 18 Jun 2008 13:27:00 -0700 (PDT) Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 7446928C1D2 for ; Wed, 18 Jun 2008 13:27:00 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.27,667,1204531200"; d="scan'208";a="58257451" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-2.cisco.com with ESMTP; 18 Jun 2008 13:27:49 -0700 Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m5IKRnDc005769 for ; Wed, 18 Jun 2008 13:27:49 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.13.8/8.13.8) with ESMTP id m5IKRntL013867 for ; Wed, 18 Jun 2008 20:27:49 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jun 2008 13:27:48 -0700 Received: from jmpolk-wxp01.cisco.com ([10.21.84.215]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jun 2008 13:27:48 -0700 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 18 Jun 2008 15:27:48 -0500 To: tsvwg From: "James M. Polk" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jun 2008 20:27:48.0628 (UTC) FILETIME=[C6330D40:01C8D181] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1497; t=1213820869; x=1214684869; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20 |Subject:=20ID=20cutoff=20dates=20and=20submission=20tool=2 0reminder |Sender:=20; bh=8/8PCJT4bD2/Bomnl9T0W/TFtJl79g2pQYvwMbVsv+k=; b=kcb0bk+OvI+SB78xRTlGJmylcnrBJgolC2sAyp7CRwAY6tPnUYHWkiaR3s szhNvoTJHiBiiAc8tt/24BOf+A6psUoLMuiPftFbiBgydBNHEBxg53KptSnd PQVZKId7Zv; Authentication-Results: sj-dkim-3; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); Subject: [Tsvwg] ID cutoff dates and submission tool reminder X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org TSVWG This is a reminder of the cut-off dates for draft submission for IETF-72: - Monday, July 7th for -00s by 17:00 PDT (24:00 UTC/GMT) - Monday, July 14th for -01+ by 17:00 PDT (24:00 UTC/GMT) **NOTICE THE *DEADLINE* TIME CHANGE FOR SUBMISSIONS** Yes, that's right, we have 13 additional hours (each deadline) to work on submissions (oh, the possibilities...!) Refer here for complete details: http://www.ietf.org/meetings/72/72-cutoff_dates.html So, these dates are just a few weeks off and our WG agenda is due on July 16th (less than a month away). Also, please use the tool to upload your document: https://datatracker.ietf.org/idst/upload.cgi It will be published very, very quickly this way, but I will note that it does not check for ALL the nits, so it's a good idea to run idnits before submitting: http://tools.ietf.org/tools/idnits/ Also, please send me a note if you want agenda time to present an ID. I, again, will be building the agenda for TSVWG, and I'm not that good at reading people's minds to know that they meant to submit a request. Once the agenda time is used up, it is used up. Agenda time preference will be given to TSVWG items. Don't surprise me with a request for agenda time on July 28th, given that official agendas are due on the 16th. Cheers, James IETF TSVWG co-chair *********************************** "It should NEVER be inconvenient to do the right thing" From tsvwg-bounces@ietf.org Wed Jun 25 08:14:50 2008 Return-Path: X-Original-To: tsvwg-archive@optimus.ietf.org Delivered-To: ietfarch-tsvwg-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F4AD3A686E; Wed, 25 Jun 2008 08:14:50 -0700 (PDT) X-Original-To: tsvwg@core3.amsl.com Delivered-To: tsvwg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 800253A686E; Wed, 25 Jun 2008 08:14:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.39 X-Spam-Level: X-Spam-Status: No, score=-5.39 tagged_above=-999 required=5 tests=[AWL=0.859, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 B3SH9MGPtx9t; Wed, 25 Jun 2008 08:14:48 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 72BE03A680B; Wed, 25 Jun 2008 08:14:48 -0700 (PDT) Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 80F6120543; Wed, 25 Jun 2008 17:14:49 +0200 (CEST) X-AuditID: c1b4fb3e-ab993bb000004ec0-4a-486260e92fed Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 71FEA204D2; Wed, 25 Jun 2008 17:14:49 +0200 (CEST) Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jun 2008 17:15:17 +0200 Received: from [127.0.0.1] ([147.214.183.142]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Jun 2008 17:15:17 +0200 Message-ID: <486260E8.4050406@ericsson.com> Date: Wed, 25 Jun 2008 17:14:48 +0200 From: Magnus Westerlund User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Magnus Westerlund References: <482B01E3.40802@ericsson.com> In-Reply-To: <482B01E3.40802@ericsson.com> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 25 Jun 2008 15:15:17.0513 (UTC) FILETIME=[468E3790:01C8D6D6] X-Brightmail-Tracker: AAAAAA== Cc: tsvwg , l3vpn@ietf.org Subject: Re: [Tsvwg] Call for adopting draft-davie-tsvwg-rsvp-l3vpn as a TSVWG item X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: tsvwg-bounces@ietf.org Errors-To: tsvwg-bounces@ietf.org To conclude this call for adoption. There is sufficient support and no disagreement that we adopt it. Thereby it is adopted as a WG item. Cheers Magnus Magnus Westerlund skrev: > At the last IETF meeting there was discussion on adopting "Support for > RSVP in Layer 3 VPNs" as WG item. > http://tools.ietf.org/id/draft-davie-tsvwg-rsvp-l3vpn-02.txt > > This starts a 2 week consensus call if TSVWG should adopt this document > with the goal of publishing it as proposed standard. Please express your > views. > > Cheers > > Magnus Westerlund > > IETF Transport Area Director & TSVWG Chair > ---------------------------------------------------------------------- > Multimedia Technologies, Ericsson Research EAB/TVM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 8 4048287 > Färögatan 6 | Fax +46 8 7575550 > S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > > -- Magnus Westerlund IETF Transport Area Director & TSVWG Chair ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Färögatan 6 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------