Re: Proposed agenda for IPv6 Operations - IETF 77

Fred Baker <fred@cisco.com> Sun, 21 March 2010 05:32 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 740A43A686D for <ietfarch-v6ops-archive@core3.amsl.com>; Sat, 20 Mar 2010 22:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.414
X-Spam-Level:
X-Spam-Status: No, score=-108.414 tagged_above=-999 required=5 tests=[AWL=-1.649, 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_HI=-8, RDNS_NONE=0.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 2dc105bPrXSx for <ietfarch-v6ops-archive@core3.amsl.com>; Sat, 20 Mar 2010 22:32:51 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 1E2BF3A6810 for <v6ops-archive@lists.ietf.org>; Sat, 20 Mar 2010 22:32:51 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1NtDhY-0006Vk-ON for v6ops-data0@psg.com; Sun, 21 Mar 2010 05:27:52 +0000
Received: from [171.71.176.117] (helo=sj-iport-6.cisco.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <fred@cisco.com>) id 1NtDhV-0006VY-Dw for v6ops@ops.ietf.org; Sun, 21 Mar 2010 05:27:49 +0000
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAD9LpUurR7H+/2dsb2JhbACbOXOgRpgYhH0Egx4
X-IronPort-AV: E=Sophos;i="4.51,281,1267401600"; d="scan'208";a="500144537"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-6.cisco.com with ESMTP; 21 Mar 2010 05:27:48 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o2L5RmsJ018498; Sun, 21 Mar 2010 05:27:48 GMT
Subject: Re: Proposed agenda for IPv6 Operations - IETF 77
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="windows-1252"
From: Fred Baker <fred@cisco.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A64951224D7B@XCH-NW-01V.nw.nos.boeing.com>
Date: Sat, 20 Mar 2010 22:27:47 -0700
Cc: IPv6 Operations <v6ops@ops.ietf.org>, Ron Bonica <ron@bonica.org>, Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2AB0B1CD-6E10-4EA5-9793-FA4039828993@cisco.com>
References: <2A0BDC9E-9C5A-4D75-83E6-C7D058264CAC@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A64951224D7B@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1077)
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

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