multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Dmitry Anipko <Dmitry.Anipko@microsoft.com> Mon, 14 November 2011 05:21 UTC
Return-Path: <Dmitry.Anipko@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB0381F0C42 for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 f2vfipoQFbmx for <ipv6@ietfa.amsl.com>; Sun, 13 Nov 2011 21:21:17 -0800 (PST)
Received: from smtp.microsoft.com (mailb.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0D61F0C44 for <ipv6@ietf.org>; Sun, 13 Nov 2011 21:21:16 -0800 (PST)
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (157.54.80.61) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sun, 13 Nov 2011 21:21:11 -0800
Received: from TK5EX14MBXC266.redmond.corp.microsoft.com ([169.254.2.128]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.01.0355.003; Sun, 13 Nov 2011 21:21:11 -0800
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Thread-Topic: multiple policy tables handling in draft-ietf-6man-addr-select-opt-01
Thread-Index: AcyijTWX59zcnPnKTYaF1gdIRytzuw==
Date: Mon, 14 Nov 2011 05:21:11 +0000
Message-ID: <03FE6A726D13284495EF1787D25F1DF9018D7907@TK5EX14MBXC266.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.71]
Content-Type: multipart/alternative; boundary="_000_03FE6A726D13284495EF1787D25F1DF9018D7907TK5EX14MBXC266r_"
MIME-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 14 Nov 2011 05:21:22 -0000
Hello,
I have a question about this text the -01 revision:
>>A node MAY use OPTION_DASP in any of the following two cases:
1: The address selection option is delivered across a secure, trusted
channel.
The OPTION_DASP is configured by a network administrator, presumably based on some knowledge they have about what makes more or less sense in the particular network. How whether or not a secure channel has been used on one of the networks relates to whether or not the admin of that network has knowledge of a completely different network the host may simultaneously be connected to?
Thanks,
Dmitry
- multiple policy tables handling in draft-ietf-6ma… Dmitry Anipko
- Re: multiple policy tables handling in draft-ietf… Arifumi Matsumoto
- RE: multiple policy tables handling in draft-ietf… Dmitry Anipko
- Re: multiple policy tables handling in draft-ietf… Arifumi Matsumoto