Re: [Sigtran] Optional RC configured on one side and not the other
"Brian F. G. Bidulock" <bidulock@openss7.org> Tue, 19 November 2013 07:43 UTC
Return-Path: <bidulock@openss7.org>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com
(Postfix) with ESMTP id C3D531AC4A5 for <sigtran@ietfa.amsl.com>;
Mon, 18 Nov 2013 23:43:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxrbQmBPx31W for
<sigtran@ietfa.amsl.com>; Mon, 18 Nov 2013 23:43:09 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [142.59.210.7]) by
ietfa.amsl.com (Postfix) with ESMTP id 099621A8034 for <sigtran@ietf.org>;
Mon, 18 Nov 2013 23:43:08 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net
[192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP
id rAJ7gxU3021727; Tue, 19 Nov 2013 00:42:59 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by
wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id
rAJ7gx83022177; Tue, 19 Nov 2013 00:42:59 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net
(8.14.3/8.14.3/Submit) id rAJ7gxf1022176; Tue, 19 Nov 2013 00:42:59 -0700
Date: Tue, 19 Nov 2013 00:42:59 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Richard Knowles <richardk@adax.com>
Message-ID: <20131119074259.GA21962@openss7.org>
Mail-Followup-To: Richard Knowles <richardk@adax.com>, sigtran@ietf.org
References: <Pine.LNX.4.64.1311181020000.3090@adax.adax>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.64.1311181020000.3090@adax.adax>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: sigtran@ietf.org
Subject: Re: [Sigtran] Optional RC configured on one side and not the other
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: bidulock@openss7.org
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>,
<mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sigtran/>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>,
<mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 07:43:11 -0000
Richard, Richard Knowles wrote: (Mon, 18 Nov 2013 10:24:25) > > Assume you have the conditions (one AS, etc.) to allow RC to be > optional, does the RFC permit one side (IPSP SE mode for example) to > still send an RC and the other to not include an RC? I think the > answer is yes, but I can't find an explicit reference permitting it. Nothing forbidding it either. Whether RC is included or not could even vary on a message-by-message basis from either ASP. --brian -- Brian F. G. Bidulock bidulock@openss7.org http://www.openss7.org/
- [Sigtran] Optional RC configured on one side and … Richard Knowles
- Re: [Sigtran] Optional RC configured on one side … Brian F. G. Bidulock
- Re: [Sigtran] Optional RC configured on one side … Richard Knowles