draft-yhb-6man-ra-privacy-flag-02
"Yu Hua bing" <yhb810501@gmail.com> Wed, 16 March 2011 13:47 UTC
Return-Path: <yhb810501@gmail.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 97D323A6999 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 06:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.717
X-Spam-Level:
X-Spam-Status: No, score=-2.717 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_00=-2.599, HTML_MESSAGE=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 FefeRXetBQTW for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 06:47:03 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 52D503A698F for <ipv6@ietf.org>; Wed, 16 Mar 2011 06:47:03 -0700 (PDT)
Received: by vxg33 with SMTP id 33so1929135vxg.31 for <ipv6@ietf.org>; Wed, 16 Mar 2011 06:48:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; bh=nxvmSor3obFgFUPU0375kC5BUy4S+1DIYXqQX1l9VLQ=; b=OdrFBV/KEXQOTZwdgAfluP/mxwIUQYg8I3My63xnsD8PutezyMgQN4KO0p9q9Fnz/X C9srAdyVKT7FMlWjqXv6gPG6ZrdTKyGy1TJDVJHZzHLHHKPKyE8JmcT5JZ6uzeY+EiY0 L0qseDvh9p3E9wION9rkfTBvJ/23x/HEyBn/8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; b=LbWDSBCQN5+pCfzbQtpwOF3fbXAghEfy23ZQ9y6EGYTJCMa9nBk7V9DTzeAxd8Il6F kNn6cX/HcDgXcltn/0RjTL4mL8vGemiGUEPUcbIjQqwqt/OEP4y13YBiGjcOooucwco0 1jFN/coCreXRRNcywrAFEjAQiaN8Q4QVgWepQ=
Received: by 10.220.186.131 with SMTP id cs3mr6895vcb.38.1300283309177; Wed, 16 Mar 2011 06:48:29 -0700 (PDT)
Received: from yhbPC ([220.200.24.149]) by mx.google.com with ESMTPS id n13sm343386vcr.41.2011.03.16.06.48.25 (version=SSLv3 cipher=OTHER); Wed, 16 Mar 2011 06:48:28 -0700 (PDT)
Message-ID: <42CE6F8FB47047BC917B7A168B33ED86@yhbPC>
From: Yu Hua bing <yhb810501@gmail.com>
To: ipv6@ietf.org
Subject: draft-yhb-6man-ra-privacy-flag-02
Date: Wed, 16 Mar 2011 21:48:11 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CBE423.D822D1E0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
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, 16 Mar 2011 13:47:04 -0000
Hi, please read the following words.After you read the words, you may agree that the DisablePrivacy flag is helpful. RFC 4941 3.6. Deployment Considerations Devices implementing this specification MUST provide a way for the end user to explicitly enable or disable the use of temporary addresses. In addition, a site might wish to disable the use of temporary addresses in order to simplify network debugging and operations. Consequently, implementations SHOULD provide a way for trusted system administrators to enable or disable the use of temporary addresses. Additionally, sites might wish to selectively enable or disable the use of temporary addresses for some prefixes. For example, a site might wish to disable temporary address generation for "Unique local" [ULA] prefixes while still generating temporary addresses for all other global prefixes. Another site might wish to enable temporary address generation only for the prefixes 2001::/16 and 2002::/16, while disabling it for all other prefixes. To support this behavior, implementations SHOULD provide a way to enable and disable generation of temporary addresses for specific prefix subranges. This per- prefix setting SHOULD override the global settings on the node with respect to the specified prefix subranges. Note that the pre-prefix setting can be applied at any granularity, and not necessarily on a per-subnet basis. The use of temporary addresses may cause unexpected difficulties with some applications. As described below, some servers refuse to accept communications from clients for which they cannot map the IP address into a DNS name. In addition, some applications may not behave robustly if temporary addresses are used and an address expires before the application has terminated, or if it opens multiple sessions, but expects them to all use the same addresses. Consequently, the use of temporary addresses SHOULD be disabled by default in order to minimize potential disruptions. Individual applications, which have specific knowledge about the normal duration of connections, MAY override this as appropriate.
- draft-yhb-6man-ra-privacy-flag-02 Yu Hua bing
- Re: draft-yhb-6man-ra-privacy-flag-02 Brian Haberman
- Re: draft-yhb-6man-ra-privacy-flag-02 Mark Smith
- Re: draft-yhb-6man-ra-privacy-flag-02 huabing yu
- Re: draft-yhb-6man-ra-privacy-flag-02 huabing yu
- Re: draft-yhb-6man-ra-privacy-flag-02 Mark Smith
- Re: draft-yhb-6man-ra-privacy-flag-02 Yu Hua bing
- Re: draft-yhb-6man-ra-privacy-flag-02 Brian E Carpenter
- Re: draft-yhb-6man-ra-privacy-flag-02 Bob Hinden
- Re: draft-yhb-6man-ra-privacy-flag-02 Mark Smith
- Re: draft-yhb-6man-ra-privacy-flag-02 Brian E Carpenter
- Re: draft-yhb-6man-ra-privacy-flag-02 sthaug
- Re: draft-yhb-6man-ra-privacy-flag-02 Mark Smith
- Re: draft-yhb-6man-ra-privacy-flag-02 sthaug
- Re: draft-yhb-6man-ra-privacy-flag-02 Mark Smith
- draft-yhb-6man-ra-privacy-flag-02 Yu Hua bing