Re: [apps-discuss] APPSDIR review of draft-ietf-v6ops-ipv6-discard-prefix

S Moonesamy <sm+ietf@elandsys.com> Wed, 11 January 2012 19:22 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0874B21F874F for <apps-discuss@ietfa.amsl.com>; Wed, 11 Jan 2012 11:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level:
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90JOGCySN+Yh for <apps-discuss@ietfa.amsl.com>; Wed, 11 Jan 2012 11:22:42 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D38F421F8750 for <apps-discuss@ietf.org>; Wed, 11 Jan 2012 11:22:41 -0800 (PST)
Received: from SUBMAN.elandsys.com ([41.136.237.192]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q0BJMOrm001189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2012 11:22:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1326309758; i=@elandsys.com; bh=fvbclxw8TQHKvC+RYv3dLIVXOB8lDaMPCoPY49b8b7s=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=ZdBO1At8R6/Qfe9OLh6XD+F86mhJVuBUMXcQfeTMXIrr61wljBA5P+pm4xAPV0Aqc UcP+T13WyPjRajQ4gaNn+BMOFMar0iVlUlhwH9ZnI8M30JRQgo4bWSmntQV+kP/EWG BrldQfqN3EbEZXHYTRFugGlX6A8k7+hT9g1sFfo0=
Message-Id: <6.2.5.6.2.20120111074406.0b203d58@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 11 Jan 2012 07:54:40 -0800
To: Nick Hilliard <nick@inex.ie>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <4F0D7EC8.90603@inex.ie>
References: <6.2.5.6.2.20120110143618.09180b88@elandnews.com> <4F0D7EC8.90603@inex.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: draft-ietf-v6ops-ipv6-discard-prefix.all@tools.ietf.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-v6ops-ipv6-discard-prefix
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2012 19:22:46 -0000

Hi Nick,
At 04:21 11-01-2012, Nick Hilliard wrote:
>this document requests another special ipv6 address prefix, which is what
>RFC5156 is all about.  So it's appropriate that it mentions that it's
>updating RFC5156, no?

Yes.  The last sentence in the Abstract Section contains "updates 
RFC5156 by explaining".  The Introduction Section does not contain a 
similar explanation.

I consider my comments as addressed.

Regards,
S. Moonesamy