
From mayer@ntp.org  Sun Mar 29 10:31:11 2009
Return-Path: <mayer@ntp.org>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E7A73A6BAE; Sun, 29 Mar 2009 10:31:11 -0700 (PDT)
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=[AWL=-0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, WHOIS_NETSOLPR=0.001]
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 T4Go7rXHBsWK; Sun, 29 Mar 2009 10:31:10 -0700 (PDT)
Received: from mail2.ntp.org (mail2.ntp.org [204.152.184.138]) by core3.amsl.com (Postfix) with ESMTP id 787C23A6BF6; Sun, 29 Mar 2009 10:31:10 -0700 (PDT)
Received: from firewall.antoniuk.lan (mail.antoniuk.md [65.86.158.146]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ntp.org (Postfix) with ESMTP id DEFB8398CD; Sun, 29 Mar 2009 17:32:04 +0000 (UTC) (envelope-from mayer@ntp.org)
Received: from cust-63-209-224-130.bos-dynamic.gis.net ([63.209.224.130] helo=[10.10.10.101]) by firewall.antoniuk.lan with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <mayer@ntp.org>) id 1LnyrY-0004nv-3T; Sun, 29 Mar 2009 13:32:00 -0400
Message-ID: <49CFB090.2010304@ntp.org>
Date: Sun, 29 Mar 2009 13:32:00 -0400
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Frank Sweetser <fs@WPI.EDU>
References: <C5ED799C.9EF1C%john_brzozowski@cable.comcast.com> <49C82F3F.8070902@wpi.edu>
In-Reply-To: <49C82F3F.8070902@wpi.edu>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-kostecke.net-MailScanner: Found to be clean
X-kostecke.net-MailScanner-From: mayer@ntp.org
X-Mailman-Approved-At: Thu, 02 Apr 2009 11:18:29 -0700
Cc: dhc WG <dhcwg@ietf.org>, Hemant Singh <shemant@cisco.com>, "int-area@ietf.org" <int-area@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [Int-area] [dhcwg] DHCPv6 router option
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Mar 2009 17:31:11 -0000

Frank Sweetser wrote:
> John Jason Brzozowski wrote:
>> Frank,
>>
>> Are you suggesting we specify a way in DHC to prevent people from
>> improperly
>> configuring their DHCPv6 servers?
> 
> Not at all.  I run a network full of students, so I'm thoroughly aware
> of the futility of assuming that all of your clients are well behaved
> ones =)
> 
> My point simply was that, in any network full of untrusted hosts, there
> are multiple ways for a rogue DHCP server to cause network problems,
> regardless of the existence or lack of a router DHCPv6 option.  If
> you're at all concerned about rogue DHCPv6 servers, then you absolutely
> need some form of switch based "DHCP guard" - a filter applied to all
> edge ports which prevents them from sending out the rogue DHCP
> advertisements.
> 
> So in other words, with or without the DHCPv6 router option, you still
> have to spend the time on a DHCP guard or you're going to be vulnerable
> to rogue DHCP servers.
> 

There's already a virus in the wild that is doing this. See
Trojan.Flush.M. In fact Googling for this shows that there is a new
version out:
http://arstechnica.com/security/news/2009/03/new-version-of-dns-server-trojan-flushm-spotted-in-the-pipe.ars

Though this is more about using DHCP guard everywhere.

Danny


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


From touch@ISI.EDU  Mon Apr  6 12:22:28 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1D893A6407; Mon,  6 Apr 2009 12:22:28 -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 WrDiInQesJER; Mon,  6 Apr 2009 12:22:27 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id BBAF128C133; Mon,  6 Apr 2009 12:22:27 -0700 (PDT)
Received: from [75.214.207.127] (127.sub-75-214-207.myvzw.com [75.214.207.127]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n36JM1dF020864; Mon, 6 Apr 2009 12:22:03 -0700 (PDT)
Message-ID: <49DA5659.4050401@isi.edu>
Date: Mon, 06 Apr 2009 12:22:01 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: ietf@ietf.org, "'Internet Area'" <int-area@ietf.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Dir <tsv-dir@ietf.org>
Subject: [Int-area] tsv-dir review of draft-atlas-icmp-unnumbered-06
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2009 19:22:28 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, all,

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. The authors should consider
this review together with any other last-call comments they
receive. Please always CC tsv-dir@ietf.org if you reply to or forward
this review.

The primary purpose of the document is to extend supplemental
information carried in ICMP responses to support diagnostics, notably by
supporting interface naming information. The document describes one use
of extended ICMP (RFC4884), which was developed for this purpose as well
as to support MPLS diagnostics.

This document would extend the information available to transport
protocols, notably for destination unreachable, time exceeded, and
parameter problem ICMP messages. This document does describe a use of
extended ICMPs that, if deployed widely, would provide additional
information to transport protocols which could be useful diagnostically,
but is not expected to impact the operation of these transport protocols.

Issues of backward compatibility of legacy transports with extended
ICMPs are discussed in Section 5.1 of RFC4884, and is not affected by
the particular extension described in this document. This document does
describe a use of extended ICMPs that would be expected to be seen by
legacy transport protocols, however.

For stateful transports, such as TCP, SCTP, and DCCP, the extended ICMP
described by this document could provide useful diagnostic information,
but should not affect protocol operation. UDP is not directly affected
by this extension, but is anticipated to pass the extended information
up to the application; revised traceroute applications would provide
this information, if available (i.e., on stacks that support it), to the
user.

Note that there are potential issues of interaction of extended ICMP
(RFC4884) with legacy transports, and which affect whether more than 128
bytes of header are available in the ICMP response, as well as whether
full-packet inspection (e.g., checksum verification or other
authentication) can even be performed. This further advocates for
conservative approaches in parsing ICMP responses, especially requiring
that new implementations support RFC4884 extensions and do not
anticipate a full packet in the ICMP payload. This document does not
alter that effect, but, as noted above, would be the first use of
extended ICMP expected to widely interact with transport protocols.

There is no need to modify this document to address these issues; the
are sufficiently addressed in RFC4884.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknaVlkACgkQE5f5cImnZrultgCg6qfzz3FvMk+lAlKQMaURGoqS
h6EAni49Df5WeeT4VNsgcxT6HftjuPho
=faI/
-----END PGP SIGNATURE-----

From hannu.hietalahti@nokia.com  Mon Apr  6 22:37:34 2009
Return-Path: <hannu.hietalahti@nokia.com>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A59B93A68AB; Mon,  6 Apr 2009 22:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 rebezHObI6xh; Mon,  6 Apr 2009 22:37:33 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 27A4F3A67F0; Mon,  6 Apr 2009 22:37:32 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n375cPNC020713; Tue, 7 Apr 2009 08:38:33 +0300
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 7 Apr 2009 08:38:23 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by vaebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 7 Apr 2009 08:38:18 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 7 Apr 2009 08:38:13 +0300
Received: from NOK-AM1MHUB-05.mgdnok.nokia.com (65.54.30.9) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 7 Apr 2009 07:38:12 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by NOK-AM1MHUB-05.mgdnok.nokia.com ([65.54.30.9]) with mapi; Tue, 7 Apr 2009 07:38:11 +0200
From: <hannu.hietalahti@nokia.com>
To: <rai@ietf.org>, <int-area@ietf.org>
Date: Tue, 7 Apr 2009 07:38:10 +0200
Thread-Topic: 3GPP - IETF dependency list update
Thread-Index: Acm3Qwl3W70gtbAbS7KjRaAbEGsRFA==
Message-ID: <15443028349C3C44BA819EB51B3B4F3C27F3519E5E@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_15443028349C3C44BA819EB51B3B4F3C27F3519E5ENOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Apr 2009 05:38:13.0120 (UTC) FILETIME=[0AF3A000:01C9B743]
X-Nokia-AV: Clean
Subject: [Int-area] 3GPP - IETF dependency list update
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 05:37:34 -0000

--_000_15443028349C3C44BA819EB51B3B4F3C27F3519E5ENOKEUMSG01mgd_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear all,

the 3GPP - IETF dependency document was updated during IETF #74 and the lat=
est version is available on 3GPP website: http://www.3gpp.org/IETF-Dependen=
cies-and-Priorities

I have already shared a link to the document on TSG CT mailing list in 3GPP=
 side as well as with some of my IETF contacts already. In the discussion b=
etween myself and the ADs and WG chairs of the affected IETF groups it was =
agreed to use these RAI and Internet area mailing lists for more general di=
stribution of the document.

BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724



--_000_15443028349C3C44BA819EB51B3B4F3C27F3519E5ENOKEUMSG01mgd_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"2">
<div>Dear all,</div>
<div>&nbsp;</div>
<div>the 3GPP - IETF dependency document was updated during IETF #74 and th=
e latest version is available on 3GPP website: <a href=3D"http://www.3gpp.o=
rg/IETF-Dependencies-and-Priorities"><font color=3D"#0000FF"><u>http://www.=
3gpp.org/IETF-Dependencies-and-Priorities</u></font></a></div>
<div>&nbsp;</div>
<div>I have already shared a link to the document on TSG CT mailing list in=
 3GPP side as well as with some of my IETF contacts already. In the discuss=
ion between myself and the ADs and WG chairs of the affected IETF groups it=
 was agreed to use these RAI and
Internet area mailing lists for more general distribution of the document.<=
/div>
<div>&nbsp;</div>
<div>BR,</div>
<div>Hannu Hietalahti</div>
<div>3GPP TSG CT Chairman</div>
<div>tel: &#43;358 40 5021724</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_15443028349C3C44BA819EB51B3B4F3C27F3519E5ENOKEUMSG01mgd_--

From touch@ISI.EDU  Tue Apr  7 09:58:40 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 08DD43A6832; Tue,  7 Apr 2009 09:58: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=[AWL=0.000,  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 eW+tzDE4fN2s; Tue,  7 Apr 2009 09:58:39 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 85F373A6CE1; Tue,  7 Apr 2009 09:57:47 -0700 (PDT)
Received: from [75.215.125.96] (96.sub-75-215-125.myvzw.com [75.215.125.96]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n37GwOKv008089; Tue, 7 Apr 2009 09:58:26 -0700 (PDT)
Message-ID: <49DB862F.8090307@isi.edu>
Date: Tue, 07 Apr 2009 09:58:23 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: ietf@ietf.org, "'Internet Area'" <int-area@ietf.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Dir <tsv-dir@ietf.org>
Subject: [Int-area] tsv-dir review of draft-atlas-icmp-unnumbered-06
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2009 16:58:40 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, all,

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. The authors should consider
this review together with any other last-call comments they
receive. Please always CC tsv-dir@ietf.org if you reply to or forward
this review.

The primary purpose of the document is to extend supplemental
information carried in ICMP responses to support diagnostics, notably by
supporting interface naming information. The document describes one use
of extended ICMP (RFC4884), which was developed for this purpose as well
as to support MPLS diagnostics.

This document would extend the information available to stateful
transports (TCP, SCTP, and DCCP), notably for destination unreachable,
time exceeded, and parameter problem ICMP messages. This document does
describe a use of extended ICMPs that, if deployed widely, would provide
additional information to transport protocols which could be useful
diagnostically, but is not expected to impact the operation of these
transport protocols.

Issues of backward compatibility of legacy transports with extended
ICMPs are discussed in Section 5.1 of RFC4884, and is not affected by
the particular extension described in this document. This document does
describe a use of extended ICMPs that would be expected to be seen by
legacy transport protocols, however.

For stateful transports, such as TCP, SCTP, and DCCP, the extended ICMP
described by this document could provide useful diagnostic information,
but should not affect protocol operation. UDP is not directly affected
by this extension, but is anticipated to pass the extended information
up to the application; revised traceroute applications would provide
this information, if available (i.e., on stacks that support it), to the
user.

Note that there are potential issues of interaction of extended ICMP
(RFC4884) with legacy transports, and which affect whether more than 128
bytes of header are available in the ICMP response, as well as whether
full-packet inspection (e.g., checksum verification or other
authentication) can even be performed. This further advocates for
conservative approaches in parsing ICMP responses, especially requiring
that new implementations support RFC4884 extensions and do not
anticipate a full packet in the ICMP payload. This document does not
alter that effect, but, as noted above, would be the first use of
extended ICMP expected to widely interact with transport protocols.

There is no need to modify this document to address these issues; the
are sufficiently addressed in RFC4884.

Joe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknbhi8ACgkQE5f5cImnZrsnnwCg0fpTYixwNFkYsLDfNUtdVUXD
xJAAoJPnhf5NrAkZH4kOmhPeTuAIeya2
=wSSa
-----END PGP SIGNATURE-----

From jari.arkko@piuha.net  Tue Apr 14 06:02:29 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 685243A67F9 for <int-area@core3.amsl.com>; Tue, 14 Apr 2009 06:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 99U15wJ1nALl for <int-area@core3.amsl.com>; Tue, 14 Apr 2009 06:02:25 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id A80603A67E6 for <int-area@ietf.org>; Tue, 14 Apr 2009 06:02:25 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 3888119878D; Tue, 14 Apr 2009 16:03:36 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id EFD06198671; Tue, 14 Apr 2009 16:03:35 +0300 (EEST)
Message-ID: <49E4899F.3080309@piuha.net>
Date: Tue, 14 Apr 2009 16:03:27 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>
References: <35AC9B68-E14C-40A8-93B1-35F197D49F3F@cisco.com>
In-Reply-To: <35AC9B68-E14C-40A8-93B1-35F197D49F3F@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [Int-area] WG assignments for ADs
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2009 13:02:29 -0000

For your information, here is the updated list of assignments
of the ADs to the different working groups.


Jari:

  6man
  autoconf
  dna
  ipdvb
  mext
  mip4
  mipshop
  netlmm
  pana
  pppext
  savi
  shim6
  lisp (to-be-WG)
  mif (to-be-WG)
  netext (to-be-WG)

Ralph:

  16ng
  6lowpan
  ancp
  csi
  dhc
  dnsext
  l2tpext
  l2vpn
  hip
  ntp
  pwe3
  softwire
  tictoc
  trill
  6ai (BOF or to-be-WG)


From jari.arkko@piuha.net  Mon Apr 27 06:22:51 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 642A03A69FA for <int-area@core3.amsl.com>; Mon, 27 Apr 2009 06:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level: 
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.110,  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 3AbKFqH64MDy; Mon, 27 Apr 2009 06:22:50 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 917C83A6929; Mon, 27 Apr 2009 06:22:50 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id CF1AA198723; Mon, 27 Apr 2009 16:24:10 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 92666198671; Mon, 27 Apr 2009 16:24:10 +0300 (EEST)
Message-ID: <49F5B1E2.9050803@piuha.net>
Date: Mon, 27 Apr 2009 16:23:46 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>,  "int-chairs@ietf.org" <int-chairs@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [Int-area] BOFs for IETF-75
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2009 13:22:51 -0000

Stockholm is approaching fast, at least if you want to launch a major 
activity such as a new BOF. The deadlines for approving the BOFs are in 
early June, and by that time you should already be quite far in the 
process. Please talk to the ADs as soon as possible if you have ideas 
about new work.

(Other avenues for new work include AD sponsored document submissions 
("individual submissions") and charter revisions of existing WGs. These 
are generally reserved for smaller scale changes than full blown BOF 
efforts. But talk to your chairs or ADs about these cases as well.)

Jari

