
From matsuoka.h@west.ntt.co.jp  Thu Apr  9 18:25:34 2009
Return-Path: <matsuoka.h@west.ntt.co.jp>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9BA628C142 for <ipv6@core3.amsl.com>; Thu,  9 Apr 2009 18:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.896
X-Spam-Level: *
X-Spam-Status: No, score=1.896 tagged_above=-999 required=5 tests=[AWL=0.992,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
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 ixl53avZm2U7 for <ipv6@core3.amsl.com>; Thu,  9 Apr 2009 18:25:34 -0700 (PDT)
Received: from mail-outgw.ics.aqstage.jp (mail-outgw.ics.aqstage.jp [203.211.239.2]) by core3.amsl.com (Postfix) with ESMTP id D14DB28C135 for <ipv6@ietf.org>; Thu,  9 Apr 2009 18:25:26 -0700 (PDT)
Received: from mail-gw7.noc.west.ntt.co.jp (unknown [192.168.176.30]) by mail-outgw.ics.aqstage.jp (ICSMTA) with ESMTP id 9D9C246B264 for <ipv6@ietf.org>; Fri, 10 Apr 2009 10:26:30 +0900 (JST)
Received: from mail-gw7.noc.west.ntt.co.jp (localhost [127.0.0.1]) by chk-mail-gw7.noc.west.ntt.co.jp (Postfix) with ESMTP id 7EDB817927 for <ipv6@ietf.org>; Fri, 10 Apr 2009 10:26:30 +0900 (JST)
Received: from noel.hq.west.ntt.co.jp (noel.hq.west.ntt.co.jp [10.56.1.16]) by mail-gw7.noc.west.ntt.co.jp (Postfix) with ESMTP id 17176178F2 for <ipv6@ietf.org>; Fri, 10 Apr 2009 10:26:30 +0900 (JST)
Received: (from root@localhost) by noel.hq.west.ntt.co.jp () id n3A1QS704686 for ipv6@ietf.org; Fri, 10 Apr 2009 10:26:29 +0900 (JST)
Received: from indigo.hq.west.ntt.co.jp [10.56.1.12]  by noel.hq.west.ntt.co.jp with ESMTP id LAC04614; Fri, 10 Apr 2009 10:26:28 +0900
Received: from plum (plum.hq.west.ntt.co.jp [10.56.1.13]) by indigo (Postfix) with ESMTP id 9E8F52F917 for <ipv6@ietf.org>; Fri, 10 Apr 2009 10:26:28 +0900 (JST)
Received: from plum (localhost [127.0.0.1]) by localhost.hq.west.ntt.co.jp (Postfix) with ESMTP id 4C6DC39C43 for <ipv6@ietf.org>; Fri, 10 Apr 2009 10:26:28 +0900 (JST)
Received: from v-stexp02.hq.west.ntt.co.jp (v-stexp02.hq.west.ntt.co.jp [10.56.2.77]) by plum (Postfix) with ESMTP id 17BF539C42 for <ipv6@ietf.org>; Fri, 10 Apr 2009 10:26:28 +0900 (JST)
Received: from [127.0.0.1] ([10.56.94.192]) by v-stexp02.hq.west.ntt.co.jp (epro MSA 2.0a) with ESMTP id 09041010262731001.05160 for <ipv6@ietf.org> ; Fri, 10 Apr 2009 10:26:28 +0900
Message-ID: <49DEA03A.4000304@west.ntt.co.jp>
Date: Fri, 10 Apr 2009 10:26:18 +0900
From: Hirotaka Matsuoka <matsuoka.h@west.ntt.co.jp>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Fwd: I-D Action:draft-matsuoka-multihoming-try-and-error-00.txt
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2009 01:25:34 -0000

Folks,

I've submitted this draft.

Comments are welcome.

Regards,
Hirotaka Matsuoka


> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
> 	Title           : A Try and Error type approach for multihoming
> 	Author(s)       : H. Matsuoka
> 	Filename        : draft-matsuoka-multihoming-try-and-error-00.txt
> 	Pages           : 10
> 	Date            : 2009-04-08
>
> [RFC5220] describes the possible problems which an end host may
> experience, if the end host has multiple prefixes in a single
> physical link. This document proposes a solution of so-called "try
> and error" type about these problems originated in "Source Address
> Selection" which is described in [RFC5220]. A new mechanism to
> settle almost all of these problems is described in this document,
> but actually it is not effective in some particular cases. Thus it is
> necessary for every end user/host to be able to select on/off of this
> mechanism.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-matsuoka-multihoming-try-and-error-00.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.
>   
>
> <ftp://ftp.ietf.org/internet-drafts/draft-matsuoka-multihoming-try-and-error-00.txt>
>



From prabu@hackinthebox.org  Tue Apr 14 21:07:18 2009
Return-Path: <prabu@hackinthebox.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC6BA3A6E0E for <ipv6@core3.amsl.com>; Tue, 14 Apr 2009 21:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level: 
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[AWL=-0.093, BAYES_50=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 WjMVFH5O3tiD for <ipv6@core3.amsl.com>; Tue, 14 Apr 2009 21:07:17 -0700 (PDT)
Received: from prometheus.interunix.net (prometheus.interunix.net [202.190.74.58]) by core3.amsl.com (Postfix) with SMTP id 4F03D3A6A15 for <ipv6@ietf.org>; Tue, 14 Apr 2009 21:07:16 -0700 (PDT)
Received: (qmail 99656 invoked by uid 1012); 15 Apr 2009 04:08:25 -0000
Received: from 202.190.74.58 by prometheus.interunix.net (envelope-from <prabu@hackinthebox.org>, uid 1010) with qmail-scanner-1.25-st-qms  (clamdscan: 0.87/3227. spamassassin: 3.1.8. perlscan: 1.25-st-qms.   Clear:RC:0(202.190.74.58):SA:0(-4.4/5.0):.  Processed in 3.37079 secs); 15 Apr 2009 04:08:25 -0000
X-Antivirus-INTERUNIX-Mail-From: prabu@hackinthebox.org via prometheus.interunix.net
X-Antivirus-INTERUNIX: 1.25-st-qms (Clear:RC:0(202.190.74.58):SA:0(-4.4/5.0):. Processed in 3.37079 secs Process 99648)
Received: from unknown (HELO praburaajan-selvarajans-macbook.local) (prabu@hackinthebox.org@202.190.74.58) by prometheus.interunix.net with SMTP; 15 Apr 2009 04:08:21 -0000
Message-ID: <49E55D9E.303@hackinthebox.org>
Date: Wed, 15 Apr 2009 12:07:58 +0800
From: "S. Praburaajan" <prabu@hackinthebox.org>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: ipv6@ietf.org, asterisk-security@lists.digium.com,  asterisk-users@lists.digium.com, bugtraq@securityfocus.com
Subject: HITBSecConf2009 - Malaysia: Call for Papers
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Apr 2009 04:07:18 -0000

The Call for Papers for HITB Security Conference 2009 Malaysia is now open!

Talks that are more technical or that discuss new and never before seen
attack methods are of more interest than a subject that has been covered
several times before. Summaries not exceeding 1250 words should be
submitted (in plain text format) to cfp -at- hackinthebox.org for review
and possible inclusion in the programme.

Submissions are due no later than 31st July 2009

TOPICS

Topics of interest include, but are not limited to the following:

# 3G/4G Cellular Networks
# Apple / OS X security vulnerabilities
# SS7/Backbone telephony networks
# VoIP security
# Firewall technologies
# Intrusion detection
# Data Recovery, Forensics and Incident Response
# HSDPA and CDMA Security
# WIMAX Security
# Identification and Entity Authentication
# Network Protocol and Analysis
# Smart Card and Physical Security
# Virus and Worms
# WLAN, GPS, HAM Radio, Satellite, RFID and Bluetooth Security
# Analysis of malicious code
# Applications of cryptographic techniques
# Analysis of attacks against networks and machines
# File system security
# Security of Embedded Devices
# Side Channel Analysis of Hardware Devices

PLEASE NOTE:

We do not accept product or vendor related pitches. If your talk
involves an advertisement for a new product or service your company is
offering, please do not submit.

Your submission should include:

# Name, title, address, email and phone/contact number
# Short biography, qualification, occupation (limit 250 words)
# Summary or abstract for your presentation (limit 1250 words)
# Technical requirements (video, internet, wireless, audio, etc.)

Each non-resident speaker will receive accommodation for 2 nights/3
days. For each non-resident speaker, HITB will cover travel expenses up
to USD 1,200.00.

HITBSecConf2009 - Malaysia
http://conference.hackinthebox.org/hitbsecconf2009kl/


From elevyabe@cisco.com  Thu Apr 16 00:33:40 2009
Return-Path: <elevyabe@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4FF53A6CF1 for <ipv6@core3.amsl.com>; Thu, 16 Apr 2009 00:33:40 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wFMObwP4Q524 for <ipv6@core3.amsl.com>; Thu, 16 Apr 2009 00:33:39 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 3C0643A6CE0 for <ipv6@ietf.org>; Thu, 16 Apr 2009 00:33:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,197,1238976000"; d="scan'208";a="38406113"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 16 Apr 2009 07:34:49 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n3G7YnDI016810;  Thu, 16 Apr 2009 09:34:49 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3G7YnIw010135; Thu, 16 Apr 2009 07:34:49 GMT
Received: from xmb-ams-335.cisco.com ([144.254.231.80]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 16 Apr 2009 09:34:49 +0200
Received: from [144.254.53.110] ([144.254.53.110]) by xmb-ams-335.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 16 Apr 2009 09:34:48 +0200
Message-ID: <49E6DF98.4080408@cisco.com>
Date: Thu, 16 Apr 2009 09:34:48 +0200
From: Eric Levy-Abegnoli <elevyabe@cisco.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: New version of DSL Line identification draft
References: <49B7D12F.6030503@ericsson.com>
In-Reply-To: <49B7D12F.6030503@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 16 Apr 2009 07:34:48.0743 (UTC) FILETIME=[D262BB70:01C9BE65]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2521; t=1239867289; x=1240731289; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=elevyabe@cisco.com; z=From:=20Eric=20Levy-Abegnoli=20<elevyabe@cisco.com> |Subject:=20Re=3A=20New=20version=20of=20DSL=20Line=20ident ification=20draft |Sender:=20; bh=qR1wm8U5KI9TWhckhSW596kWJrhIMrrUlAo1zZpqMmY=; b=FHw0Ephu0tXTL7VfkjcBPpB0hxW6pEmOwYnFyLp5pLAiCd0rgwNc7jVRJl qs4B/LiDktYU7yACBrUuXrUC8RpAYCWcjx7vCUHhN50MmnlIyJxxAQDJLEth Fsfz8uguS1;
Authentication-Results: ams-dkim-2; header.From=elevyabe@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; ); 
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2009 07:33:40 -0000

Hi,
I went thought the document and I have some concerns regarding 
interaction with Secure Neighbor Discovery (SeND).
I am unclear in section "Security Considerations" of the document. and 
whether it suggests SeND cannot be enabled on the DSL scenario, or just 
the option-(Line Identification Neighbor Discovery Option) is not 
protected. Neither sounds acceptable.
Assuming the latter (option not part of the signed message), I had a 
quick re-look at RFC3971and both sections 5.2.1 and 5.2.2 are in 
contradiction with what is proposed here.
In 5.2.1, "The RSA Signature option is added as the last option and in 
5.2.2, "The receiver MUST ignore any options that come after the first 
RSA Signature option"
In the context of SeND, that pretty much mandates any option to be part 
of the signed message, and pretty much prevent intermediary nodes to 
insert/delete options unless they do proxy-SeND, which is yet to be 
standardized.

Note that ignoring an option in SeND is not that easy anyway: the 
checksum is also signed. The (icmp) checksum obviously checksum the 
entire message, including the LIO. It's in 2463; section 2.3. So in 
order to ignore an LIO, the sender would have to sign a pseudo message 
containing a pseudo-checksum that would ignore the LIO. Starts to be 
very messy. And anyway, should be explained in the draft
I would suggest that you synchronize with proxy-SeND work so that AN can 
re-sign the message.
Eric

Suresh Krishnan a écrit :
> Hi Folks,
>   We have published a new version of the DSL line identification draft 
> that addresses the comments received at the last IETF meeting.
>
> * It includes a network reference diagram
> * It adds text describing the Broadband Forum TR-101 model and adds a 
> reference to the model
> * It adds text describing the n:1 vlan model that causes issues with 
> SLAAC
> * It addresses issues raised at the Broadband Forum IPv6 interim 
> meeting about adding the option in the RAs
>
> The draft is available at
>
> http://tools.ietf.org/html/draft-krishnan-6man-rs-mark-02
>
> Please take a look at the document and let us know if you have any 
> issues or suggestions or if you support this work.
>
> Thanks
> Suresh
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From fred@cisco.com  Mon Apr 20 23:40:16 2009
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C696A3A6A51 for <ipv6@core3.amsl.com>; Mon, 20 Apr 2009 23:40:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.575
X-Spam-Level: 
X-Spam-Status: No, score=-106.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 JXFh6T-3MwGk for <ipv6@core3.amsl.com>; Mon, 20 Apr 2009 23:40:15 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 9C8E43A69EB for <ipv6@ietf.org>; Mon, 20 Apr 2009 23:40:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,222,1238976000"; d="scan'208";a="42304828"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 21 Apr 2009 06:41:31 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n3L6fVhc005219;  Tue, 21 Apr 2009 02:41:31 -0400
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n3L6fU82002337; Tue, 21 Apr 2009 06:41:31 GMT
Message-Id: <B421D4DF-E9EA-4973-93B4-0128D57352D8@cisco.com>
From: Fred Baker <fred@cisco.com>
To: IPv6 Operations <v6ops@ops.ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Fwd: I-D Action:draft-baker-v6ops-greynet-00.txt 
Date: Mon, 20 Apr 2009 23:41:30 -0700
References: <20090421063001.E9D0E3A6FE3@core3.amsl.com>
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=891; t=1240296091; x=1241160091; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Fwd=3A=20I-D=20Action=3Adraft-baker-v6ops-greyn et-00.txt=20 |Sender:=20 |To:=20IPv6=20Operations=20<v6ops@ops.ietf.org>,=0A=20=20=2 0=20=20=20=20=20IETF=20IPv6=20Mailing=20List=20<ipv6@ietf.or g>; bh=WGCArPTlUmk90Wkdt3bP9vkQNGxDzcq8VTBFyjMnF5w=; b=E2X/9PUujzDRmZTV8mMuNLtebwbOHWuIgK5xlOvei3TaVCzdnRZM3UP31c ZOfwHfvYhunq4Zbt1i4oyFsd+nTEGlYM+p6cMk76o5W8HwVaWpff7Aqdlivk TMvuOHTFQ0;
Authentication-Results: rtp-dkim-1; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Cc: draft-baker-v6ops-greynet@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 06:40:16 -0000

oops, wrong list name. I'd still appreciate any thoughts folks have. :-)

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: April 20, 2009 11:30:01 PM PDT
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-baker-v6ops-greynet-00.txt
> Reply-To: internet-drafts@ietf.org
>
> A New Internet-Draft is available from the on-line Internet-Drafts  
> directories.
>
> 	Title           : IPv4 and IPv6 Greynets
> 	Author(s)       : F. Baker, et al.
> 	Filename        : draft-baker-v6ops-greynet-00.txt
> 	Pages           : 8
> 	Date            : 2009-04-20
>
> This note discusses a feature to support building Greynets for IPv4
> and IPv6.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-baker-v6ops-greynet-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/


From brian@innovationslab.net  Tue Apr 21 05:26:23 2009
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C0393A6BD9; Tue, 21 Apr 2009 05:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.753
X-Spam-Level: 
X-Spam-Status: No, score=-2.753 tagged_above=-999 required=5 tests=[AWL=-0.154, 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 QauSV7MTxAab; Tue, 21 Apr 2009 05:26:22 -0700 (PDT)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200]) by core3.amsl.com (Postfix) with ESMTP id 833BC3A6BAE; Tue, 21 Apr 2009 05:26:22 -0700 (PDT)
Received: from ([128.244.206.11]) by pilot.jhuapl.edu with ESMTP with TLS id 63GHCH1.1104489; Tue, 21 Apr 2009 08:27:36 -0400
Message-ID: <49EDBBB8.6040503@innovationslab.net>
Date: Tue, 21 Apr 2009 08:27:36 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: 6MAN Work Group Last Call Outcome:draft-stjohns-sipso-10.txt
References: <49B81B6B.8090901@innovationslab.net>
In-Reply-To: <49B81B6B.8090901@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 12:26:23 -0000

All,
      The 6MAN WG Last Call on the referenced draft has concluded. 
There is consensus to support the publication of this document as an 
Informational RFC.  I want to thank all the members of the 6MAN list who 
took the time to review and comment on this document.

Regards,
Brian

Brian Haberman wrote:
> All,
>      The following document has been submitted to the IESG as 
> publication as an Informational RFC.  In order to solicit as wide a 
> review as possible, we are holding a 2-week working group last call on 
> advancing:
> 
> 
>    Title     : Common Architecture Label IPv6 Security Option (CALIPSO)
>    Author(s) : M. StJohns
>    Filename  : draft-stjohns-sipso-11.txt
> 
> 
> as an Informational document.  Please send substantive comments to the 
> mailing list.  This last call will end on March 25, 2009.
> 
> Regards,
> Brian & Bob
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From albert.e.manfredi@boeing.com  Tue Apr 21 07:24:43 2009
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B3B03A6C80 for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 07:24:43 -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=[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 2S3vOqrSw7iE for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 07:24:42 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id 8D9E53A6DE2 for <ipv6@ietf.org>; Tue, 21 Apr 2009 07:24:42 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n3LEPmpK012517 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Apr 2009 09:25:48 -0500 (CDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n3LEPmMc018458; Tue, 21 Apr 2009 07:25:48 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com [128.225.80.27]) by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n3LEPlu7018427; Tue, 21 Apr 2009 07:25:47 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 21 Apr 2009 10:25:47 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D Action:draft-baker-v6ops-greynet-00.txt 
Date: Tue, 21 Apr 2009 10:25:45 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA906013C53@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <B421D4DF-E9EA-4973-93B4-0128D57352D8@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-baker-v6ops-greynet-00.txt 
Thread-Index: AcnCTD03QCpllJeJR82CHI0J/ibJoAAP2tsg
References: <20090421063001.E9D0E3A6FE3@core3.amsl.com> <B421D4DF-E9EA-4973-93B4-0128D57352D8@cisco.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Fred Baker" <fred@cisco.com>, "IPv6 Operations" <v6ops@ops.ietf.org>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 21 Apr 2009 14:25:47.0414 (UTC) FILETIME=[102A1360:01C9C28D]
Cc: draft-baker-v6ops-greynet@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 14:24:43 -0000

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]=20

> > This note discusses a feature to support building Greynets for IPv4
> > and IPv6.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-baker-v6ops-greynet-00.txt

In the IPv6 case, I'm not sure I understand how the "honeypot" host
would know what addresses are unused, in networks where SLAAC is used.

Also, more of an editorial nature, I believe the layer 2 nitpicks might
object to the use of "LAN" to mean "IP subnet," unless I missed
something. The IEEE definition of LAN makes it so in practice, these
days, the term only applies to the single link between the layer 2
switch and one host interface.

Bert

From tim.polk@nist.gov  Tue Apr 21 07:41:36 2009
Return-Path: <tim.polk@nist.gov>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BB9F3A6BC5; Tue, 21 Apr 2009 07:41:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.528
X-Spam-Level: 
X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.071,  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 mPiO6Vht5y4t; Tue, 21 Apr 2009 07:41:35 -0700 (PDT)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by core3.amsl.com (Postfix) with ESMTP id 50E433A68C9; Tue, 21 Apr 2009 07:41:35 -0700 (PDT)
Received: from [129.6.224.67] ([129.6.224.67]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id n3LEgiQ7019549; Tue, 21 Apr 2009 10:42:44 -0400
From: Tim Polk <tim.polk@nist.gov>
To: Brian Haberman <brian@innovationslab.net>
In-Reply-To: <49EDBBB8.6040503@innovationslab.net>
Subject: Re: 6MAN Work Group Last Call Outcome:draft-stjohns-sipso-10.txt
References: <49B81B6B.8090901@innovationslab.net> <49EDBBB8.6040503@innovationslab.net>
Message-Id: <B2E392AA-B5DD-4416-99CA-6EA63AD6BA61@nist.gov>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 21 Apr 2009 10:42:44 -0400
X-Mailer: Apple Mail (2.930.3)
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: tim.polk@nist.gov
Cc: IPv6 WG Mailing List <ipv6@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 14:41:36 -0000

Thanks!

On Apr 21, 2009, at 8:27 AM, Brian Haberman wrote:

> All,
>     The 6MAN WG Last Call on the referenced draft has concluded.  
> There is consensus to support the publication of this document as an  
> Informational RFC.  I want to thank all the members of the 6MAN list  
> who took the time to review and comment on this document.
>
> Regards,
> Brian
>
> Brian Haberman wrote:
>> All,
>>     The following document has been submitted to the IESG as  
>> publication as an Informational RFC.  In order to solicit as wide a  
>> review as possible, we are holding a 2-week working group last call  
>> on advancing:
>>   Title     : Common Architecture Label IPv6 Security Option  
>> (CALIPSO)
>>   Author(s) : M. StJohns
>>   Filename  : draft-stjohns-sipso-11.txt
>> as an Informational document.  Please send substantive comments to  
>> the mailing list.  This last call will end on March 25, 2009.
>> Regards,
>> Brian & Bob
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>


From fred@cisco.com  Tue Apr 21 07:50:09 2009
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 443ED3A6C11 for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 07:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.487
X-Spam-Level: 
X-Spam-Status: No, score=-106.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 222bq1qCrHwb for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 07:50:08 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 509A93A6BFE for <ipv6@ietf.org>; Tue, 21 Apr 2009 07:50:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,224,1238976000"; d="scan'208";a="290093075"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 21 Apr 2009 14:51:25 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n3LEpO90015541;  Tue, 21 Apr 2009 07:51:25 -0700
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3LEpO6p029494; Tue, 21 Apr 2009 14:51:24 GMT
Message-Id: <B7B891C7-EBD7-44F6-BA7D-E1E3B2B72708@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA906013C53@XCH-NE-1V2.ne.nos.boeing.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: I-D Action:draft-baker-v6ops-greynet-00.txt 
Date: Tue, 21 Apr 2009 07:51:24 -0700
References: <20090421063001.E9D0E3A6FE3@core3.amsl.com> <B421D4DF-E9EA-4973-93B4-0128D57352D8@cisco.com> <CA7D9B4A761066448304A6AFC09ABDA906013C53@XCH-NE-1V2.ne.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1325; t=1240325485; x=1241189485; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20I-D=20Action=3Adraft-baker-v6ops-greyne t-00.txt=20 |Sender:=20; bh=zWI0Noi4X1iFm6Oxvr+b0UAQKrPXY1WRZWvfaf2n2YY=; b=HXVx8XDjwZ+QBQUT8Ja8MVhi3uT/wB/JR5RfqSeOngOIh7cBx6HPoXXTvq DwPcuNG2BrLznZo1IKGh6b2lJ4u92/HDAHRD2ulTlFQzKs8DxhWKGqKE/tKs e1wFfVs0gY;
Authentication-Results: sj-dkim-3; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: IPv6 Operations <v6ops@ops.ietf.org>, draft-baker-v6ops-greynet@tools.ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 14:50:09 -0000

On Apr 21, 2009, at 7:25 AM, Manfredi, Albert E wrote:

>> -----Original Message-----
>> From: Fred Baker [mailto:fred@cisco.com]
>
>>> This note discusses a feature to support building Greynets for IPv4
>>> and IPv6.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-baker-v6ops-greynet-00.txt
>
> In the IPv6 case, I'm not sure I understand how the "honeypot" host
> would know what addresses are unused, in networks where SLAAC is used.

I would expect that it would take the router's word that no responder  
was found for the address.

> Also, more of an editorial nature, I believe the layer 2 nitpicks  
> might
> object to the use of "LAN" to mean "IP subnet," unless I missed
> something. The IEEE definition of LAN makes it so in practice, these
> days, the term only applies to the single link between the layer 2
> switch and one host interface.

Gee, in a layer 3 context, I use the term "LAN" to mean a "Local Area  
Network", a layer 2 domain, perhaps instantiated in a switch or a set  
of them, that connects some number of layer 3 devices. Examples  
include Ethernet domains, 802.11, 802.15.4, 802.16, 802.21, ...

How does the IEEE define a LAN?

I take your point that some of these probably should be translated to  
"IP Subnet".

From albert.e.manfredi@boeing.com  Tue Apr 21 08:13:30 2009
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 659DC3A6D62 for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 08:13:30 -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=[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 bvC9ARHuvFpj for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 08:13:29 -0700 (PDT)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 931DF3A6C94 for <ipv6@ietf.org>; Tue, 21 Apr 2009 08:13:29 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n3LFEcFh009022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 21 Apr 2009 08:14:38 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n3LFEca5001035; Tue, 21 Apr 2009 10:14:38 -0500 (CDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com [128.225.80.27]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n3LFEbgV001026; Tue, 21 Apr 2009 10:14:37 -0500 (CDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 21 Apr 2009 11:14:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D Action:draft-baker-v6ops-greynet-00.txt 
Date: Tue, 21 Apr 2009 11:14:36 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA906013CDA@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <B7B891C7-EBD7-44F6-BA7D-E1E3B2B72708@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-baker-v6ops-greynet-00.txt 
Thread-Index: AcnCkKYhYhFmpv/PSzKAHQr22iH6UgAACrGw
References: <20090421063001.E9D0E3A6FE3@core3.amsl.com> <B421D4DF-E9EA-4973-93B4-0128D57352D8@cisco.com> <CA7D9B4A761066448304A6AFC09ABDA906013C53@XCH-NE-1V2.ne.nos.boeing.com> <B7B891C7-EBD7-44F6-BA7D-E1E3B2B72708@cisco.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Fred Baker" <fred@cisco.com>
X-OriginalArrivalTime: 21 Apr 2009 15:14:37.0467 (UTC) FILETIME=[E29CAEB0:01C9C293]
Cc: IPv6 Operations <v6ops@ops.ietf.org>, draft-baker-v6ops-greynet@tools.ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 15:13:30 -0000

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]=20

> Gee, in a layer 3 context, I use the term "LAN" to mean a=20
> "Local Area =20
> Network", a layer 2 domain, perhaps instantiated in a switch=20
> or a set =20
> of them, that connects some number of layer 3 devices. Examples =20
> include Ethernet domains, 802.11, 802.15.4, 802.16, 802.21, ...
>=20
> How does the IEEE define a LAN?
>=20
> I take your point that some of these probably should be=20
> translated to =20
> "IP Subnet".

IEEE 802.1D says that a LAN ties together devices with MAC layers. So,
for example, an Ethernet LAN in which (layer 1) hubs interconnect the
hosts will support multiple hosts in a single LAN. But if you introduce
bridges (aka layer 2 switches), then you're tying together separate
individual LANs into a "bridged LAN," or catenet.

Clause 6 of 802.1D:

"MAC Bridges interconnect the separate IEEE 802 LANs that compose a
Bridged Local Area Network by
relaying and filtering frames between the separate MACs of the bridged
LANs."

So in today's typical networks, the LAN becomes just a single link
between one host and one switch. Seemed odd to me too, but Rich Seifert
caught me on this more than once.

What you were adressing, though, seemed to be IP subnets, i.e. networks
having common IP address prefixes. I guess that the "IP subnet" term
doesn't apply to IPv6.

Bert

From fred@cisco.com  Tue Apr 21 14:46:13 2009
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D65F3A6988 for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 14:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.483
X-Spam-Level: 
X-Spam-Status: No, score=-106.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 Lu-vbdGMhD8N for <ipv6@core3.amsl.com>; Tue, 21 Apr 2009 14:46:12 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 130543A6B9B for <ipv6@ietf.org>; Tue, 21 Apr 2009 14:45:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,226,1238976000"; d="scan'208";a="290370116"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-6.cisco.com with ESMTP; 21 Apr 2009 21:46:58 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n3LLkwm6011718;  Tue, 21 Apr 2009 17:46:58 -0400
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3LLkivL028084; Tue, 21 Apr 2009 21:46:57 GMT
Message-Id: <648F04B0-A79A-4A05-A4E4-9F8AFDB78A49@cisco.com>
From: Fred Baker <fred@cisco.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-Reply-To: <CA7D9B4A761066448304A6AFC09ABDA906013CDA@XCH-NE-1V2.ne.nos.boeing.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: I-D Action:draft-baker-v6ops-greynet-00.txt 
Date: Tue, 21 Apr 2009 14:46:57 -0700
References: <20090421063001.E9D0E3A6FE3@core3.amsl.com> <B421D4DF-E9EA-4973-93B4-0128D57352D8@cisco.com> <CA7D9B4A761066448304A6AFC09ABDA906013C53@XCH-NE-1V2.ne.nos.boeing.com> <B7B891C7-EBD7-44F6-BA7D-E1E3B2B72708@cisco.com> <CA7D9B4A761066448304A6AFC09ABDA906013CDA@XCH-NE-1V2.ne.nos.boeing.com>
X-Mailer: Apple Mail (2.930.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1928; t=1240350418; x=1241214418; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20I-D=20Action=3Adraft-baker-v6ops-greyne t-00.txt=20 |Sender:=20 |To:=20=22Manfredi,=20Albert=20E=22=20<albert.e.manfredi@bo eing.com>; bh=dZTFyOR8ndRE8SaMaTp84bxfhpBHnm4gBiUBzIdfkCA=; b=f+nuDfKS+MmS62S5QDHswTVtveKtRJFcas6+hwdSRpJBgkSE1vGG9JKHB5 1zHw2ur/4Ldc6zFhaZtAeC2Ne+QiyGLrtkH0EZHdaB6eICOxSy/QHM0ty3t1 gesEYOZN8l;
Authentication-Results: rtp-dkim-2; header.From=fred@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: IPv6 Operations <v6ops@ops.ietf.org>, draft-baker-v6ops-greynet@tools.ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2009 21:46:13 -0000

So you are saying that the legal definition of a LAN ("a network which  
crosses no legal boundary"), vs the legal definition of a WAN (" a  
network that crosses a legal boundary") is irrelevant, and the only  
agency that defines LANs is IEEE 802? I can think of some folks that  
might take exception to that.

I say that as someone who was building MAC bridges before the term was  
coined...

On Apr 21, 2009, at 8:14 AM, Manfredi, Albert E wrote:

>> -----Original Message-----
>> From: Fred Baker [mailto:fred@cisco.com]
>
>> Gee, in a layer 3 context, I use the term "LAN" to mean a
>> "Local Area
>> Network", a layer 2 domain, perhaps instantiated in a switch
>> or a set
>> of them, that connects some number of layer 3 devices. Examples
>> include Ethernet domains, 802.11, 802.15.4, 802.16, 802.21, ...
>>
>> How does the IEEE define a LAN?
>>
>> I take your point that some of these probably should be
>> translated to
>> "IP Subnet".
>
> IEEE 802.1D says that a LAN ties together devices with MAC layers. So,
> for example, an Ethernet LAN in which (layer 1) hubs interconnect the
> hosts will support multiple hosts in a single LAN. But if you  
> introduce
> bridges (aka layer 2 switches), then you're tying together separate
> individual LANs into a "bridged LAN," or catenet.
>
> Clause 6 of 802.1D:
>
> "MAC Bridges interconnect the separate IEEE 802 LANs that compose a
> Bridged Local Area Network by
> relaying and filtering frames between the separate MACs of the bridged
> LANs."
>
> So in today's typical networks, the LAN becomes just a single link
> between one host and one switch. Seemed odd to me too, but Rich  
> Seifert
> caught me on this more than once.
>
> What you were adressing, though, seemed to be IP subnets, i.e.  
> networks
> having common IP address prefixes. I guess that the "IP subnet" term
> doesn't apply to IPv6.
>
> Bert


From alh-ietf@tndh.net  Wed Apr 22 11:11:19 2009
Return-Path: <alh-ietf@tndh.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBC943A6CB3 for <ipv6@core3.amsl.com>; Wed, 22 Apr 2009 11:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.634
X-Spam-Level: ***
X-Spam-Status: No, score=3.634 tagged_above=-999 required=5 tests=[AWL=-1.748,  BAYES_50=0.001, DNS_FROM_RFC_BOGUSMX=1.482, FH_HOST_EQ_D_D_D_D=0.765,  HOST_EQ_STATICB=1.372, MISSING_SUBJECT=1.762]
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 bmp90zyvhsI9 for <ipv6@core3.amsl.com>; Wed, 22 Apr 2009 11:11:19 -0700 (PDT)
Received: from tndh.net (static-66-15-163-216.bdsl.verizon.net [66.15.163.216]) by core3.amsl.com (Postfix) with ESMTP id 7BDDC3A7141 for <ipv6@ietf.org>; Wed, 22 Apr 2009 11:11:10 -0700 (PDT)
Received: from eagle (192.168.123.10:1666) by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server] id <S180C90A> for <ipv6@ietf.org> from <alh-ietf@tndh.net>; Wed, 22 Apr 2009 11:12:24 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'IPv6 WG Mailing List'" <ipv6@ietf.org>
Subject: 
Date: Wed, 22 Apr 2009 11:12:17 -0700
Message-ID: <040001c9c375$ded598e0$9c80caa0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnDdd6Hus1RqzNuR1SJALildLzzRg==
Content-Language: en-us
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: alh-ietf@tndh.net
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2009 18:11:20 -0000

A new draft is available for discussion:

http://www.ietf.org/internet-drafts/draft-hain-ipv6-fwrh-00.txt


From night@nist.gov  Fri Apr 24 14:04:04 2009
Return-Path: <night@nist.gov>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C079C3A6BD3; Fri, 24 Apr 2009 14:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level: 
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 nlpUvHonQke2; Fri, 24 Apr 2009 14:04:03 -0700 (PDT)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by core3.amsl.com (Postfix) with ESMTP id 91E4E3A6A56; Fri, 24 Apr 2009 14:04:03 -0700 (PDT)
Received: from [127.0.0.1] (81-140.antd.nist.gov [129.6.140.81]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id n3OL41aF011689; Fri, 24 Apr 2009 17:04:16 -0400
Message-ID: <49F22940.8000109@nist.gov>
Date: Fri, 24 Apr 2009 17:04:00 -0400
From: Stephen Nightingale <night@nist.gov>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: sp500-273-comments@antd.nist.gov
Subject: Announcing a USGv6 Testing meeting on May 27th
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: night@nist.gov
X-Mailman-Approved-At: Fri, 24 Apr 2009 15:47:34 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2009 21:07:29 -0000

To all IPv6 aficionados,

Please find attached the calling notice for a public meeting to be held 
at NIST on May 27th 2009, for the USGv6 Testing Program.
Feel free to forward this notice and the attached documents to any 
persons or groups who may be interested but note that the room can hold 
a maximum of 60 persons, and priority is given to Accreditors, 
prospective USGv6 test laboratories and IPv6 test developers.

Regards,

Stephen Nightingale
USGv6 Testing Program

============================================================

*Announcing a public meeting at NIST to discuss the rollout of the USGv6
Testing Program.*

NIST invites interested parties including laboratory accreditors,
testing laboratories and test equipment suppliers to attend a meeting
regarding the USGv6 testing program. The purpose of the meeting is to
resolve comments on the guidance document, NIST SP 500-273 and on the
test specifications for the USG profile, and to launch the testing program.

DATE OF THE MEETING:  May 27th 2009 from 9am till 5pm.

LOCATION: NIST, 100 Bureau Drive, Gaithersburg, MD 20899, Building 101,
Lecture Room A. Directions can be found on the main NIST website at:
http://www.nist.gov/public_affairs/maps/nistmaps.html

PROVISIONAL AGENDA:
1.	USG IPv6 testing program elements.
2.	Test Laboratory Accreditation Issues
	a.	Quality issues – by ISO 17025.
	b.	Technical Methods – by NIST SP 500-273.
	c.	Test specifications.
	d.	Gaps – Overlaps – Fit.
	e.	Interlaboratory comparisons considering multiple accreditors.
3.	Supplier’s Declaration of Conformity
	a.	Test laboratories separately encouraged to list products passed.
4.	Test program management issues.
5.	Discussion.


FOR FURTHER INFORMATION CONTACT: Stephen Nightingale,
sp500-273-comments@antd.nist.gov.

ADDITIONAL INFORMATION:
•	The USGv6 testing website will be updated soon, and well before the
meeting. URL is: http://www.antd.nist.gov/usgv6/testing.html.
•	The guidance document (NIST SP 500-273) has been the subject of a
separate announcement.
•	All intending participants must register in advance to gain access to
the campus. There is a limit of 60 participants constrained by the size
of the room.  Precedence will be given to the first 2 representatives of
each Accreditation body, IPv6 testing laboratory, and IPv6 test
equipment supplier. For the balance, we may need to limit participation
to 1 representative per organization, and on a first come first served
basis.  Please indicate your organization’s potential role, designate
your primary representative and register early in case we need to make
this selection. Access to the NIST campus and the room cannot be
guaranteed for unregistered participants.




From Jinmei_Tatuya@isc.org  Wed Apr 29 17:08:31 2009
Return-Path: <Jinmei_Tatuya@isc.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A3F73A6E40 for <ipv6@core3.amsl.com>; Wed, 29 Apr 2009 17:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.889
X-Spam-Level: 
X-Spam-Status: No, score=0.889 tagged_above=-999 required=5 tests=[AWL=0.289,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, NO_RELAYS=-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 brcL+xsuoOaS for <ipv6@core3.amsl.com>; Wed, 29 Apr 2009 17:08:30 -0700 (PDT)
Received: from mon.jinmei.org (mon.jinmei.org [IPv6:2001:4f8:3:36::162]) by core3.amsl.com (Postfix) with ESMTP id EECBE3A6BC0 for <ipv6@ietf.org>; Wed, 29 Apr 2009 17:08:29 -0700 (PDT)
Received: from jmb.jinmei.org (unknown [IPv6:2001:4f8:3:bb:217:f2ff:fee0:a91f]) by mon.jinmei.org (Postfix) with ESMTP id 60CA633C2E; Wed, 29 Apr 2009 17:09:51 -0700 (PDT)
Date: Wed, 29 Apr 2009 17:09:51 -0700
Message-ID: <m2hc07gfxs.wl%Jinmei_Tatuya@isc.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <Jinmei_Tatuya@isc.org>
To: shemant@cisco.com, wbeebee@cisco.com, erik.nordmark@sun.com
Subject: comments on draft-ietf-6man-ipv6-subnet-model-03
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2009 00:08:31 -0000

Upon request from the author, I've reviewed the I-D, and here are my
comments.

I have one top level comment: I'm okay with removing the following two
bullets from the original "on-link" definition of RFC4861

          - a Neighbor Advertisement message is received for the
          (target) address, or
          - any Neighbor Discovery message is received from the address.

to address security concerns.  But then I'd like to further simplify
the rule of processing incoming NSes by discarding ones if the source
address is not on-link.  Removing the above bullets while allowing
accepting incoming NSes from a non-on-link address (and responding to
them) could make implementation very tricky for very little benefit.

Some implementations have already adopted this "simplification" to
address the security concern, and, realistically, I don't think we can
convince the maintainer to cancel the change and introduce a
trickier patch to support the very minor case.  The end result would
be the same: we'll lose interoperability.  Of course, we could blame
such implementations for being "non compliant", but IMO it's more
productive to plug the tricky corner case as we'll probably never need
it in practice.

Other technical comments:

- Section 1 doesn't explain the motivation of removing the last two
  bullets of on-link definition.  I actually expected such
  incompleteness because it was not in the original goal of this
  draft.  That's why I insisted that this part is in a separate
  document.

- Section 1:
  Due to the tricky implication on on-link vs being neighbor (see
  above), if we wanted to keep it (note that I'm against it) the
  following cannot hold:

     A host only performs address resolution for IPv6 addresses that are
     on-link.

  because the host would have to perform address resolution for a
  "neighbor" but not necessarily an on-link node.  (if we also remove
  the tricky implication, this can be automatically solved:-)

- Section 2: the section title "Host Behavior" is not very indicative
   to me.

- Section 2: I simply didn't understand the following paragraph at
  all.  Please elaborate (I guess I asked the same thing before and it
  hasn't improved)

   2.  Note that Redirects cannot signal that an address is off-link.
   [...]

- Section 3, bullet 3.  I disagree with this bullet as stated above.
  I won't go into further details on this at the moment because it's a
  rather meta level issue.

- Section 3, bullet 6: I don't understand this at all.  Why is this
  mentioned?  Why only multicast?

- Section 3, bullet 7: this rule isn't enforceable.  I thought I
  already pointed it out before (please google it).

- Section 4, last para:

   Using cached on-link determination information without first
   [...]

  This doesn't address my previous concern.  Besides, this is not
  really a "rule" even if it's in the "host rules" section.

- Section 6: I guess there should be a reference to the security
  problem (cert advisory or something).

Editorial comments:

- Section 1 first para
  s/a address/an address/
- Some of the acronyms should be expanded beforehand (ND, RA, etc)
- there are some redundant white spaces, e.g. "on- link" (should be
  on-link)
- Section 3, bullet 4, there seems to be an indentation problem:

          Similarly, the following text from section 6.2.5 of [RFC4861]

  I suspect it's not part of citation.
  
---
JINMEI, Tatuya
Internet Systems Consortium, Inc.

From shemant@cisco.com  Thu Apr 30 10:56:59 2009
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 54ABB3A6F7F for <ipv6@core3.amsl.com>; Thu, 30 Apr 2009 10:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.667
X-Spam-Level: 
X-Spam-Status: No, score=-5.667 tagged_above=-999 required=5 tests=[AWL=0.932,  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 1AzE4WsF3cmm for <ipv6@core3.amsl.com>; Thu, 30 Apr 2009 10:56:57 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id A35C63A6D97 for <ipv6@ietf.org>; Thu, 30 Apr 2009 10:56:57 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,274,1238976000"; d="scan'208";a="43043576"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 30 Apr 2009 17:58:20 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n3UHwKQI006366;  Thu, 30 Apr 2009 13:58:20 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n3UHwKvs003909; Thu, 30 Apr 2009 17:58:20 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 30 Apr 2009 13:58:20 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: RE: comments on draft-ietf-6man-ipv6-subnet-model-03
Date: Thu, 30 Apr 2009 13:58:18 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D07093E25@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m2hc07gfxs.wl%Jinmei_Tatuya@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comments on draft-ietf-6man-ipv6-subnet-model-03
Thread-Index: AcnJJ/7IEDd4tBbTQVaOf9Q5xUh1igAlFpIg
References: <m2hc07gfxs.wl%Jinmei_Tatuya@isc.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: =?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIzpIGyhC?= <Jinmei_Tatuya@isc.org>,  "Wes Beebee (wbeebee)" <wbeebee@cisco.com>, <erik.nordmark@sun.com>
X-OriginalArrivalTime: 30 Apr 2009 17:58:20.0119 (UTC) FILETIME=[3F162E70:01C9C9BD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1258; t=1241114300; x=1241978300; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=shemant@cisco.com; z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco. com> |Subject:=20RE=3A=20comments=20on=20draft-ietf-6man-ipv6-su bnet-model-03 |Sender:=20 |To:=20=3D?ISO-2022-JP?B?SklOTUVJIFRhdHV5YSAvIBskQj9ATEBDIz pIGyhC?=3D=20<Jinmei_Tatuya@isc.org>,=0A=20=20=20=20=20=20=2 0=20=22Wes=20Beebee=20(wbeebee)=22=20<wbeebee@cisco.com>,=20 <erik.nordmark@sun.com>; bh=sId4guh04gLgieXIXcIV0E5NWBjAJ1Jgdbij6Xj8fxk=; b=MLQzTf6dugBCagjS5/sdKoOg2oTibIgUtZqxtPUhumPp2ZVTQAHjJcHC4t QsRLJgrJUP+8/snroE3rlLcw+9lVmbMtYbigiG/B57KjpWUfJJBYhUDEoToJ S3+UhmGk7+;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); 
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2009 17:56:59 -0000

Jinmei,

Thanks much for the review.  I think you have some section numbers mixed up from our draft in your review.  I have snipped below all of your comments where I believe section numbers could be wrong.  Could you please go thru the section numbers below and fix them for us and then we'd be happy to respond to your comments.  I think where you say "Section 4" it is Section 3. Likewise for "Section 3, bullet 7" and "Section 3 bullet 6" should be "Section 2, bullet 6 and 7". We really weren't sure about "Section 3, bullet 3" because both sections 2 and 3 in our document have a bullet 3.


- Section 3, bullet 3.  I disagree with this bullet as stated above.
  I won't go into further details on this at the moment because it's a
  rather meta level issue.

- Section 3, bullet 6: I don't understand this at all.  Why is this
  mentioned?  Why only multicast?

- Section 3, bullet 7: this rule isn't enforceable.  I thought I 
  already pointed it out before (please google it).

- Section 4, last para:

   Using cached on-link determination information without first
   [...]

  This doesn't address my previous concern.  Besides, this is not
  really a "rule" even if it's in the "host rules" section.


Thanks,

Hemant

From Jinmei_Tatuya@isc.org  Thu Apr 30 12:13:52 2009
Return-Path: <Jinmei_Tatuya@isc.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 311DE3A6BC8 for <ipv6@core3.amsl.com>; Thu, 30 Apr 2009 12:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.86
X-Spam-Level: 
X-Spam-Status: No, score=0.86 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, NO_RELAYS=-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 FGlmD95qxO1K for <ipv6@core3.amsl.com>; Thu, 30 Apr 2009 12:13:51 -0700 (PDT)
Received: from mon.jinmei.org (mon.jinmei.org [IPv6:2001:4f8:3:36::162]) by core3.amsl.com (Postfix) with ESMTP id 4897E3A69F0 for <ipv6@ietf.org>; Thu, 30 Apr 2009 12:13:51 -0700 (PDT)
Received: from jmb.jinmei.org (unknown [IPv6:2001:4f8:3:bb:217:f2ff:fee0:a91f]) by mon.jinmei.org (Postfix) with ESMTP id 0195C33C2E; Thu, 30 Apr 2009 12:15:12 -0700 (PDT)
Date: Thu, 30 Apr 2009 12:15:12 -0700
Message-ID: <m2zldyeywv.wl%Jinmei_Tatuya@isc.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <Jinmei_Tatuya@isc.org>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: comments on draft-ietf-6man-ipv6-subnet-model-03
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D07093E25@xmb-rtp-20e.amer.cisco.com>
References: <m2hc07gfxs.wl%Jinmei_Tatuya@isc.org> <B00EDD615E3C5344B0FFCBA910CF7E1D07093E25@xmb-rtp-20e.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: erik.nordmark@sun.com, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2009 19:13:52 -0000

At Thu, 30 Apr 2009 13:58:18 -0400,
"Hemant Singh (shemant)" <shemant@cisco.com> wrote:

> Thanks much for the review.  I think you have some section numbers
> mixed up from our draft in your review.  I have snipped below all of
> your comments where I believe section numbers could be wrong.  Could
> you please go thru the section numbers below and fix them for us and
> then we'd be happy to respond to your comments.  I think where you
> say "Section 4" it is Section 3. Likewise for "Section 3, bullet 7"
> and "Section 3 bullet 6" should be "Section 2, bullet 6 and 7". We
> really weren't sure about "Section 3, bullet 3" because both
> sections 2 and 3 in our document have a bullet 3.

Oops, my bad.  I've fixed the reference error below.

> - Section 3, bullet 3.  I disagree with this bullet as stated above.
>   I won't go into further details on this at the moment because it's a
>   rather meta level issue.

I meant Section 2, bullet 3 here.

> - Section 3, bullet 6: I don't understand this at all.  Why is this
>   mentioned?  Why only multicast?

I meant Section 2, bullet 6 here.

> - Section 3, bullet 7: this rule isn't enforceable.  I thought I 
>   already pointed it out before (please google it).

I meant Section 2, bullet 7 here.

> - Section 4, last para:

I meant Section 3 here.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.
