RE: Proposed agenda for IPv6 Operations - IETF 77
"Templin, Fred L" <Fred.L.Templin@boeing.com> Sun, 21 March 2010 14:04 UTC
Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D07903A691D for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 21 Mar 2010 07:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.407
X-Spam-Level:
X-Spam-Status: No, score=-4.407 tagged_above=-999 required=5 tests=[AWL=-1.642, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1]
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 kslsgJ9JREn0 for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 21 Mar 2010 07:04:29 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 3BE623A6918 for <v6ops-archive@lists.ietf.org>; Sun, 21 Mar 2010 07:04:29 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1NtLk9-0003Nk-RY for v6ops-data0@psg.com; Sun, 21 Mar 2010 14:03:05 +0000
Received: from [130.76.96.56] (helo=stl-smtpout-01.boeing.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <Fred.L.Templin@boeing.com>) id 1NtLk6-0003NE-OS for v6ops@ops.ietf.org; Sun, 21 Mar 2010 14:03:02 +0000
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o2LE2mU3004270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 21 Mar 2010 09:02:48 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o2LE2mWQ015439; Sun, 21 Mar 2010 09:02:48 -0500 (CDT)
Received: from XCH-NWHT-06.nw.nos.boeing.com (xch-nwht-06.nw.nos.boeing.com [130.247.25.110]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o2LE2l70015436 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Sun, 21 Mar 2010 09:02:48 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-06.nw.nos.boeing.com ([130.247.25.110]) with mapi; Sun, 21 Mar 2010 07:02:47 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fred Baker <fred@cisco.com>
CC: IPv6 Operations <v6ops@ops.ietf.org>, Ron Bonica <ron@bonica.org>, Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Date: Sun, 21 Mar 2010 07:02:44 -0700
Subject: RE: Proposed agenda for IPv6 Operations - IETF 77
Thread-Topic: Proposed agenda for IPv6 Operations - IETF 77
Thread-Index: AcrIt0BvQgb8cyBfS1qIJodhEYPLJwAR6OrQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A64951224DAC@XCH-NW-01V.nw.nos.boeing.com>
References: <2A0BDC9E-9C5A-4D75-83E6-C7D058264CAC@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951224D7B@XCH-NW-01V.nw.nos.boeing.com> <2AB0B1CD-6E10-4EA5-9793-FA4039828993@cisco.com>
In-Reply-To: <2AB0B1CD-6E10-4EA5-9793-FA4039828993@cisco.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
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>
Fred, As far as I can tell, the SAM proposal is a new transitional technology and protocol also. RANGER and SAM are addressing very similar problem spaces, and I think their eligibility for inclusion in the v6ops agenda should be considered on equal terms. Thanks - Fred fred.l.templin@boeing.com > -----Original Message----- > From: Fred Baker [mailto:fred@cisco.com] > Sent: Saturday, March 20, 2010 10:28 PM > To: Templin, Fred L > Cc: IPv6 Operations; Ron Bonica; Kurt Erik Lindqvist > Subject: Re: Proposed agenda for IPv6 Operations - IETF 77 > > I have a question on these. > > Per the abstract of VET, "VET can also be considered as version 2 of the Intra-Site Automatic Tunnel > Addressing Protocol (i.e., "ISATAPv2")." I tend to agree; with routing, next hop determination, and a > "Subnetwork Encapsulation and Adaptation Layer (SEAL)", I don't think this is an operational > description. I think this belongs discussed in rrg, rtgarea/rtgwg, or *maybe* int-area. > > How about you and I discuss this Monday and you convince me that this is within the charter of IPv6 > Operations. I think it is that which was explicitly placed outside the charter - transitional > technologies and protocol development. > > > On Mar 20, 2010, at 2:31 AM, Templin, Fred L wrote: > > > Fred, > > > > The new agenda posted on the webpages does not seem to match the one > > you posted to the list: > > > > http://www.ietf.org/proceedings/10mar/agenda/v6ops.html > > > > Seeing that there are new additions, I would like to propose to add the > > RANGER, VET and SEAL trilogy - preferably as the final session on > > Friday, as I have two other conflicts for the earlier portion of that session. > > The talk would require 15min, and would cover all three documents > > together (i.e., not as three separate talks). The documents are here: > > > > http://www.ietf.org/rfc/rfc5720.txt > > http://tools.ietf.org/html/draft-templin-intarea-vet > > http://tools.ietf.org/html/draft-templin-intarea-seal > > > > Thanks - Fred > > fred.l.templin@boeing.com > > > > From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On Behalf Of Fred Baker > > Sent: Tuesday, March 16, 2010 2:06 PM > > To: IPv6 Operations > > Subject: Proposed agenda for IPv6 Operations - IETF 77 > > > > Comments please... Basically I am putting three security issues and two 3GPP-relevant drafts on > Monday morning and the remainder on Friday morning. Each discussion gets about half an hour. If time > permits in the meeting, I'll pull agenda items forward from Friday to Monday. I have two drafts on > here that were not marked for v6ops but the authors asked me to include; next time I'd appreciate it > if folks used the draft-*-v6ops-* naming convention; it makes my job easier. If I have missed > anything, let me know. > > IPv6 Operations - IETF 77 > > > > Monday 22 March, 9:00 AM > > > > Agenda bashing > > > > Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential > IPv6 Internet Service > > 18-Feb-10, <draft-ietf-v6ops-cpe-simple-security-09.txt> > > Advanced Security for IPv6 CPE > > 8-Mar-10, <draft-vyncke-advanced-ipv6-security-01.txt> > > Routing Loops using ISATAP and 6to4: Problem Statement and Proposed Solutions > > 1-Feb-10, <draft-nakibly-v6ops-tunnel-loops-01.txt> > > > > IPv6 in 3GPP Evolved Packet System > > 24-Feb-10, <draft-korhonen-v6ops-3gpp-eps-01.txt> > > Mobile Networks Considerations for IPv6 Deployment > > 8-Mar-10, <draft-koodli-ipv6-in-mobile-networks-01.txt> > > Friday 26 March, 9:00 AM > > > > Emerging Service Provider Scenarios for IPv6 Deployment > > 23-Feb-10, <draft-carpenter-v6ops-isp-scenarios-01.txt> > > Unicast Transmission of IPv6 Multicast Messages on Link-layer > > 15-Feb-10, <draft-gundavelli-v6ops-l2-unicast-00.txt> > > Neighbor Cache Protection in Neighbor Discovery Protocol > > 2-Mar-10, <draft-jiang-v6ops-nc-protection-01.txt> > > DHCPv6 Prefix Delegation as IPv6 Migration Tool in Cellular Networks > > 16-Feb-10, <draft-sarikaya-v6ops-prefix-delegation-00.txt> > > Advanced Requirements for IPv6 Customer Edge Routers > > 8-Mar-10, <draft-wbeebee-v6ops-ipv6-cpe-router-bis-02.txt> > > > > > > http://www.ipinc.net/IPv4.GIF > > > > http://www.ipinc.net/IPv4.GIF
- Proposed agenda for IPv6 Operations - IETF 77 Fred Baker
- Re: Proposed agenda for IPv6 Operations - IETF 77 Naoki Matsuhira
- RE: Proposed agenda for IPv6 Operations - IETF 77 Templin, Fred L
- Re: Proposed agenda for IPv6 Operations - IETF 77 Fred Baker
- Re: Proposed agenda for IPv6 Operations - IETF 77 Fred Baker
- RE: Proposed agenda for IPv6 Operations - IETF 77 Templin, Fred L
- Re: Proposed agenda for IPv6 Operations - IETF 77 Rémi Després
- RE: Proposed agenda for IPv6 Operations - IETF 77 Templin, Fred L