Re: [Pana] Explicit error indication

Jari Arkko <jari.arkko@piuha.net> Mon, 30 May 2011 09:12 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: pana@ietfa.amsl.com
Delivered-To: pana@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3E55E06AE for <pana@ietfa.amsl.com>; Mon, 30 May 2011 02:12:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level:
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brGRESr97pZJ for <pana@ietfa.amsl.com>; Mon, 30 May 2011 02:12:38 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 763B7E0779 for <pana@ietf.org>; Mon, 30 May 2011 02:12:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2A2722CC49; Mon, 30 May 2011 12:12:36 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id reLmnPmirMUO; Mon, 30 May 2011 12:12:35 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 6C0E72CC2F; Mon, 30 May 2011 12:12:35 +0300 (EEST)
Message-ID: <4DE35F83.1070503@piuha.net>
Date: Mon, 30 May 2011 12:12:35 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
References: <4D5AA4A7.3050104@toshiba.co.jp> <4DDCE436.2010507@piuha.net> <4DDDA869.204@toshiba.co.jp> <4DDDDE0B.4070601@piuha.net> <4DE31809.1040100@toshiba.co.jp> <4DE33DAA.9060307@piuha.net> <00a001cc1ea6$e40b4510$ac21cf30$@yegin@yegin.org>
In-Reply-To: <00a001cc1ea6$e40b4510$ac21cf30$@yegin@yegin.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: pana@ietf.org, 'Ralph Droms' <rdroms@cisco.com>
Subject: Re: [Pana] Explicit error indication
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2011 09:12:38 -0000

I'm fine with using existing messages as well. In fact, that would 
probably be better.

Jari

Alper Yegin kirjoitti:
> For relaying already relayed messages... The Result-Code AVP (something like
> MULTIPLE-RELAYING-DISALLOWED) would be included in the PRY message sent from
> one PRE to the other.
> In response to a PRY that was received from the latter one.
>
> How seq no and PANA SA are used for PRY is already defined. There'd not be
> any special considerations here.
>
> Right?
>
>
> The other Result-Code would be something like RELAY-REJECTED-NO-PAA-INFO.
> This can be carried in a PAR in response to the PCI received from the PaC.
> (Defining it in response to any other message is less justified [why would
> PER lose the PAA info in the middle of a session relaying?], and also less
> trivial [what would the session id be set to??]
>
> I'm trying to see if we can achieve this with the minimum impact. 
>
> I don't think we need a new message. We just need new Result-Codes.
>
>
> We shouldn't have to touch RFC 5191.
>
> Alper
>
>
>
>
>
>  
>
>
>
>
>
>
>
>
>
>
>   
>> -----Original Message-----
>> From: pana-bounces@ietf.org [mailto:pana-bounces@ietf.org] On Behalf Of
>> Jari Arkko
>> Sent: Monday, May 30, 2011 9:48 AM
>> To: Yoshihiro Ohba
>> Cc: Ralph Droms; pana@ietf.org
>> Subject: Re: [Pana] Explicit error indication
>>
>> That would work for me.
>>
>> Jari
>>
>> Yoshihiro Ohba kirjoitti:
>>     
>>> Let me start a new thread on this subject.
>>>
>>> I remember a ZigBee member asked if explicit error indication can be
>>> sent by a PRE when a PANA message cannot be relayed for some reasons
>>> (buffer shortage, no route to PAA, etc.).  I think it would be useful
>>> to add such a feature if there is little impact to RFC 5191 to
>>>       
>> support
>>     
>>> the feature, as it could reduce unnecessarily retransmissions of PCIs
>>> from PaCs.  Reduce unnecessarily retransmissions may be good for
>>> resource constrained networks such as ZigBee.
>>>
>>> Explicit error indication can be by means of a new PANA message or a
>>> new Result-Code.
>>>
>>> Processing explicit error indication is like handling
>>> exceptions/interruptions.  So considerations would be necessarily
>>> not to interfere with the PANA sequence number processing rule.
>>> Especially this would be the case where an error indication is
>>> protected by a PANA SA.  I would expect that we don't need to support
>>> protected error indication as it would require a complex sequence
>>> number processing rule such as a separate sequence number space
>>> dedicated to error indications.
>>>
>>> IMHO, a new PANA message (e.g., PANA-Error-Indication)
>>> carrying sequence number of zero (0) may be simple, something like
>>>       
>> this:
>>     
>>> PaC     PRE
>>>     --->     PCI
>>>     <---     PEI[Error-Code="Relay-failed"] // seqno=0
>>>
>>> PEI message is unprotected and it can be used only as a hint.
>>>
>>> Regards,
>>> Yoshihiro Ohba
>>>
>>> (2011/05/26 13:58), Jari Arkko wrote:
>>>
>>>       
>>>> Yoshihiro,
>>>>
>>>>
>>>>         
>>>>> Let me give some time to analyze the impact of this recommendation.
>>>>>
>>>>>
>>>>>           
>>>> Ok. I' not claiming that my solution is necessarily the way forward,
>>>>         
>> but
>>     
>>>> I am worried about the issue.
>>>>
>>>> Jari
>>>>
>>>>
>>>>
>>>>         
>>>
>>>       
>> _______________________________________________
>> Pana mailing list
>> Pana@ietf.org
>> https://www.ietf.org/mailman/listinfo/pana
>>     
>
>
>