IETF Logo Mail Archive

Re: [dispatch] Fwd: New Version Notification for draft-procter-dispatch-outbound-discovery-00.txt

Michael Procter <michael.ietf@gmail.com> Tue, 09 September 2014 08:33 UTC

Return-Path: <michael.ietf@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50BE01A885C for <dispatch@ietfa.amsl.com>; Tue, 9 Sep 2014 01:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 C3qbnIHIgmMy for <dispatch@ietfa.amsl.com>; Tue, 9 Sep 2014 01:33:10 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F211E1A8853 for <dispatch@ietf.org>; Tue, 9 Sep 2014 01:33:09 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id z12so2271475wgg.28 for <dispatch@ietf.org>; Tue, 09 Sep 2014 01:33:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=S0jsGAYmIFnDrJBUZGuuSri4fpRraj07zIJUXcgiip8=; b=tJFRaEz0Fy5Tu+xLrQbt9e2iG9bxQWhgo62exTlRW2cvYPph5YgaDuKF/EWjeY0INR TFnqNFzIU0tmZ2T5DHzL8OWOWX7Us/DKgpPRr/qMmkXvTB9z8aiZd81F/EYp2CBoigEh miQYuXOnZz+dbhk5VkbNg1VzoxRd0j1GxerOfIawbDyVHUfVb6va0SXxrbktH8BqLNYS 58J5tCQjIF5Qd9TKh9vM1RIVG4Zz/kFGuX32eQlnvl4F0wdWqSAyoZKRmCTx2IRd3iOB 4NGZBfHOfRnGXylAIgppnbh9CCRjqNOBWZhT1C/sxJfVxvq8D9G/bNKNpgzUma8aPQMI GlBA==
MIME-Version: 1.0
X-Received: by 10.180.211.36 with SMTP id mz4mr20384097wic.39.1410251588596; Tue, 09 Sep 2014 01:33:08 -0700 (PDT)
Received: by 10.194.39.231 with HTTP; Tue, 9 Sep 2014 01:33:08 -0700 (PDT)
In-Reply-To: <5409E5BD.8010007@alum.mit.edu>
References: <20140704155153.17916.76121.idtracker@ietfa.amsl.com> <CAPms+wR0hrfiw6gWsCxRNHU=Puqw-9wVJyue08cBCKv2+jVN8g@mail.gmail.com> <201408272134.s7RLYMMS026386@hobgoblin.ariadne.com> <CALiegf=520M1pM-W9+p=N4rqeKSG121jtj9oXo7nuDF22QQf8Q@mail.gmail.com> <201409031526.s83FQiXf000720@hobgoblin.ariadne.com> <D02C8475.130A4D%jon.peterson@neustar.biz> <5409E5BD.8010007@alum.mit.edu>
Date: Tue, 09 Sep 2014 09:33:08 +0100
Message-ID: <CANyXLXaFqh2n3gcJ6JTzuSc1msp=RAv6k=qvM5F4U+o-uJbu1g@mail.gmail.com>
From: Michael Procter <michael.ietf@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dispatch/tQ9pmbODHNY05Qze3krWmzeQwCA
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] Fwd: New Version Notification for draft-procter-dispatch-outbound-discovery-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 08:33:11 -0000

Hi Paul,

On 5 September 2014 17:33, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> Another potential issue is the use of Service-Route during registration. Is
> there any way that it can be compatible with outbound?

>From a quick reading of RFC3608, I can't see any particular reason
that it would be incompatible with outbound.  As far as I can tell, a
Service-Route is expected to be used for new dialogs, and not to
modify how registrations are routed, so I don't think they interact.
Happy to be corrected by those more familiar with the mechanism
though.

Michael

v2.39.1 | Report a Bug | By Email | System Status