IETF Logo Mail Archive

Re: [mif] a question about rfc6418

<pierrick.seite@orange.com> Wed, 21 December 2011 09:42 UTC

Return-Path: <pierrick.seite@orange.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 2A0FA21F84F9 for <mif@ietfa.amsl.com>; Wed, 21 Dec 2011 01:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level:
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 dzOHJQYnkd6V for <mif@ietfa.amsl.com>; Wed, 21 Dec 2011 01:42:37 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id 5332921F84DD for <mif@ietf.org>; Wed, 21 Dec 2011 01:42:37 -0800 (PST)
Received: from r-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id DC4F25D88B7; Wed, 21 Dec 2011 10:42:35 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail2.rd.francetelecom.com (Postfix) with ESMTP id CF0825D88B3; Wed, 21 Dec 2011 10:42:35 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Wed, 21 Dec 2011 10:42:35 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCBFC4.DE36343C"
Date: Wed, 21 Dec 2011 10:42:34 +0100
Message-ID: <843DA8228A1BA74CA31FB4E111A5C462021AAEF7@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <OFB2BDD39D.C68275BF-ON4825796D.0034B867-4825796D.0034F852@zte.com.cn>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [mif] a question about rfc6418
Thread-Index: Acy/xGDdmLdgyDmNQZ6xzB5ErDEsXgAADP4Q
References: <OFB2BDD39D.C68275BF-ON4825796D.0034B867-4825796D.0034F852@zte.com.cn>
From: pierrick.seite@orange.com
To: zhou.sujing@zte.com.cn, mif@ietf.org
X-OriginalArrivalTime: 21 Dec 2011 09:42:35.0977 (UTC) FILETIME=[DED30B90:01CCBFC4]
Subject: Re: [mif] a question about rfc6418
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: Wed, 21 Dec 2011 09:42:38 -0000

Hi,

 

Nothing particular, this sentence reflects what the user is currently experiencing when getting access via a captive portal.

 

Pierrick

 

De : mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] De la part de zhou.sujing@zte.com.cn
Envoyé : mercredi 21 décembre 2011 10:38
À : mif@ietf.org
Objet : [mif] a question about rfc6418

 


    in Section 4.4 

      The network requires a web-based authentication (e.g., the access
      network is a WiFi hot spot).  In this case, the user can only
      access a captive portal.  For instance, the network may perform
      HTTP redirection or modify DNS behavior (Section 4.1 <http://tools.ietf.org/html/rfc6418#section-4.1> ) until the
      user has not authenticated.

   I am quite confused by the last word. Is it possible a typo or something particular? 


Regards~~~

-Sujing Zhou

v2.23.0 | Report a Bug | By Email