IETF Logo Mail Archive

Re: [16NG] ipv6 over ipv6cs document approval

Behcet Sarikaya <behcetsarikaya@yahoo.com> Fri, 23 November 2007 22:09 UTC

Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivgih-0007AD-0B; Fri, 23 Nov 2007 17:09:55 -0500
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1Ivgif-00079z-64 for 16ng-confirm+ok@megatron.ietf.org; Fri, 23 Nov 2007 17:09:53 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ivgie-00079l-Qw for 16ng@ietf.org; Fri, 23 Nov 2007 17:09:52 -0500
Received: from web84105.mail.mud.yahoo.com ([68.142.206.192]) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1Ivgie-0002TG-CK for 16ng@ietf.org; Fri, 23 Nov 2007 17:09:52 -0500
Received: (qmail 79275 invoked by uid 60001); 23 Nov 2007 22:01:29 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=jbpoiasSfl432sHxURAnB/i5KZEvJR3o48NEUui2WoKhWtOQ2s0yin/YehTVTDEIpoCc2wc+qVKsxaUFfgedqCU8c8Uh4SGsxkPcq2Lohr+Ns8/gziwfO2Wyg3GLcGpBWTUvb8/wg4pnOTzlJtb7O+ANPOT6M2T0+RQNo3VDAr0=;
X-YMail-OSG: ZtX9G9kVM1kwvJOsUxngOXdtblcqrOhZMFjSkH8gGUxDou.mfQBzY3nymzI3GR8hlw5FVQ--
Received: from [71.123.247.57] by web84105.mail.mud.yahoo.com via HTTP; Fri, 23 Nov 2007 14:01:29 PST
X-Mailer: YahooMailRC/818.27 YahooMailWebService/0.7.152
Date: Fri, 23 Nov 2007 14:01:29 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [16NG] ipv6 over ipv6cs document approval
To: Jari Arkko <jari.arkko@piuha.net>
MIME-Version: 1.0
Message-ID: <382616.78265.qm@web84105.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1869518428=="
Errors-To: 16ng-bounces@ietf.org

I agree that ipv6 over ipv6cs document is ready to become an RFC.
Ohe other issues however, probably, it takes a draft. Then we can see if there is really a problem there or not.

Regards,

Behcet

----- Original Message ----
From: Jari Arkko <jari.arkko@piuha.net>
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: "Premec, Domagoj" <domagoj.premec@siemens.com>om>; Junghoon Jee <junghoon.jee@gmail.com>om>; 16ng@ietf.org
Sent: Friday, November 23, 2007 12:16:15 PM
Subject: Re: [16NG] ipv6 over ipv6cs document approval



Domagoj, Syam, etc have already explained how this
works. There's really no issue.

It is true that RA intervals are something watch for; that's
why the document allowed raising them.

(In addition, at upper layers, one might consider firewall
policies regarding packets from the Internet to the hosts.)

Jari





_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng

v2.8.7 | Report a Bug | By Email