Re: [mif] Network Access Identifier
Erik Kline <ek@google.com> Tue, 19 March 2013 10:17 UTC
Return-Path: <ek@google.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0233321F88CF for <mif@ietfa.amsl.com>; Tue, 19 Mar 2013 03:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.809
X-Spam-Level:
X-Spam-Status: No, score=-102.809 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 M+PfYohgqKJ1 for <mif@ietfa.amsl.com>; Tue, 19 Mar 2013 03:17:06 -0700 (PDT)
Received: from mail-oa0-f54.google.com (mail-oa0-f54.google.com [209.85.219.54]) by ietfa.amsl.com (Postfix) with ESMTP id D078B21F84BC for <mif@ietf.org>; Tue, 19 Mar 2013 03:17:03 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id n12so256549oag.13 for <mif@ietf.org>; Tue, 19 Mar 2013 03:17:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=FZJLXbAdHtNT84TyhDjB6kW8guVZHA1L2VBg4BPOl70=; b=AbAQajzBQ6HXYE7BRwbd/mqH/4H1FryUcgVB/PiihQx+GZRL3wuHYgjiEBHo/utf8b XNsPiIHpDefGdJdNkZnA58BCDyElimxNqXVbmEWhOE+JX5wIeYm5pxk9Dejk/CMhYitU UNNSrZt1YidSGKhyR5l/rwxuH+3juNZDOZmqRr5aX3W/rFaWuyz2HBHpDh2+C4unK+s/ nwENcZfVHU7tIXVW8YA0tQLCNhuWtS/5yQm3R1f2MuKWzRJmNKMyFU8IjS7od/VJB9Dm e7JmTndME7Jw8xQYMHgCg/+wXxnQXiOm3YFF/KMyAHE88bB6JzpWfsnu4IS/q9Kb9W3J LvwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=FZJLXbAdHtNT84TyhDjB6kW8guVZHA1L2VBg4BPOl70=; b=P6uYiy7Z14GnFIRwz1mHKaAzNljuyVLC405jZuQCXfr3Z15C9gzZfSMUBZsBWrWPWd TBty0OAlTYwIlz00HmrPnslXRLiRnMbjwM3Tm8tASj0+FCyDyun5hEPZYth+G/AH0SEU 7+DenXIvzrZOLbPQ9eDiRAWikG6CBeVveIY2GPiGsOc6zOJkj9VVxXhGH9MGYPKCe2bt KoPu0sUj/C/aaEfRjryHKYZ06x/SdnawU+4f8BXJ/88+e3ef6RMm1BkbplEsyyCoxOl7 rEPbGiTuQy/H7wQ3X8TX5YKvAVxeJaNm+R262FNIAI8sYwaoc0aVT2yHaoMhAjXMZq/4 XSVA==
X-Received: by 10.182.194.35 with SMTP id ht3mr849987obc.39.1363688223404; Tue, 19 Mar 2013 03:17:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.50.227 with HTTP; Tue, 19 Mar 2013 03:16:43 -0700 (PDT)
In-Reply-To: <CANF0JMA5RoUp3orHR9qZ2fxZyZZz7Ncx4mBM6TZ5Qr6xZq3TSA@mail.gmail.com>
References: <CAAedzxrvhYonGJPSP_bKcMaJbhUJfh2q6J+J1w96uc635RYa2g@mail.gmail.com> <CANF0JMA5RoUp3orHR9qZ2fxZyZZz7Ncx4mBM6TZ5Qr6xZq3TSA@mail.gmail.com>
From: Erik Kline <ek@google.com>
Date: Tue, 19 Mar 2013 06:16:43 -0400
Message-ID: <CAAedzxoCRONyxj8Dt5oknuY-6RBbrMfZHmmm1OtvV4ManLuW9A@mail.gmail.com>
To: Hui Deng <denghui02@gmail.com>
Content-Type: multipart/alternative; boundary="f46d0444e899240aa804d8446810"
X-Gm-Message-State: ALoCoQknaK4LVHQ3+lpK9RIfhjkUjUYgp5wr2ojjzflw+bCXL9VdKGR2R1MvjyZ95T5Sif8A0w7xsCfcrkeWo+oAVlXts9xEgeX3mA0Ydn+BJap5xsYIYU3Ms3iHoCW2ppPtRooYr8ReWnkk/g3Oawa/aF19Vi/hD/W+sgjgLMV5TYVyhkE+zBj7qS9FKCqPjUSFVN0dqGwz
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] Network Access Identifier
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Mar 2013 10:17:07 -0000
Hui, By "security/trust issue" I would guess that you mean the provider needs some way to verify that the provisioning profile requested by the user can and should actually be provided (they've paid for it, they're who they say they are, ...). If so, that sounds like a perfectly normal AAA type of concern. If provisioning domains are like "static facts" about the network(s) then AAA is likely less of a concern (or possibly not a concern at all). But if a client can request/select from among a set of available provisioning domains then AAA issues will likely follow. Interesting. Thanks.
- [mif] Network Access Identifier Erik Kline
- Re: [mif] Network Access Identifier Hui Deng
- Re: [mif] Network Access Identifier Erik Kline