Re: [Pana] Explicit error indication

"Alper Yegin" <alper.yegin@yegin.org> Mon, 30 May 2011 08:52 UTC

Return-Path: <alper.yegin@yegin.org>
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 1053FE06A0 for <pana@ietfa.amsl.com>; Mon, 30 May 2011 01:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.15
X-Spam-Level:
X-Spam-Status: No, score=-101.15 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, 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 qlsOLzyGZXdL for <pana@ietfa.amsl.com>; Mon, 30 May 2011 01:52:24 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE6BE067A for <pana@ietf.org>; Mon, 30 May 2011 01:52:24 -0700 (PDT)
Received: from ibm (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0M7ZVP-1Peu1Q0Ntf-00wWbN; Mon, 30 May 2011 04:52:20 -0400
From: Alper Yegin <alper.yegin@yegin.org>
To: 'Jari Arkko' <jari.arkko@piuha.net>, 'Yoshihiro Ohba' <yoshihiro.ohba@toshiba.co.jp>
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>
In-Reply-To: <4DE33DAA.9060307@piuha.net>
Date: Mon, 30 May 2011 11:52:12 +0300
Message-ID: <00a001cc1ea6$e40b4510$ac21cf30$@yegin>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcwelY6z5mGsAfdcQtOa3rjbBXkHCAADd10w
Content-Language: en-us
x-cr-hashedpuzzle: AyKw Gh/J HnrB T5gR V4We YdZh Z5vv a7kp ejFr euEx gcFc hgIg kDWK kZgn khNN lc9J; 4; agBhAHIAaQAuAGEAcgBrAGsAbwBAAHAAaQB1AGgAYQAuAG4AZQB0ADsAcABhAG4AYQBAAGkAZQB0AGYALgBvAHIAZwA7AHIAZAByAG8AbQBzAEAAYwBpAHMAYwBvAC4AYwBvAG0AOwB5AG8AcwBoAGkAaABpAHIAbwAuAG8AaABiAGEAQAB0AG8AcwBoAGkAYgBhAC4AYwBvAC4AagBwAA==; Sosha1_v1; 7; {10771D96-069A-46E0-AA85-891E9C6BDFD2}; YQBsAHAAZQByAC4AeQBlAGcAaQBuAEAAeQBlAGcAaQBuAC4AbwByAGcA; Mon, 30 May 2011 08:51:56 GMT; UgBFADoAIABbAFAAYQBuAGEAXQAgAEUAeABwAGwAaQBjAGkAdAAgAGUAcgByAG8AcgAgAGkAbgBkAGkAYwBhAHQAaQBvAG4A
x-cr-puzzleid: {10771D96-069A-46E0-AA85-891E9C6BDFD2}
X-Provags-ID: V02:K0:QlMkjsn1wLJwLrq0Ys9UB75WdOaNeOzY/o18weSoALo uPciyx2rQURVv+Gw9Y+1b+RuTrDBNss1LLarBUssJ5iMf94CPd /ZXUb031m1UC8tRvMooo4VRfrAov9xPafXXCv9tdA+I6PX8WTK MRy2VW/FRAEWG+3nniMXSF3u0YuXeKKtAlRLx4yuA9iYorT1jY FYEXXURzC6ITdQDtGfTvBpDYUfW92fC/+L9w8/tU8c=
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 08:52:25 -0000

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