Re: [sipcore] #2: Editorial: section 2 is really confusing
"Worley, Dale R (Dale)" <dworley@avaya.com> Tue, 31 August 2010 18:39 UTC
Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43F1A3A69E5 for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 11:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.406
X-Spam-Level:
X-Spam-Status: No, score=-102.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1+9zExwShyn for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 11:39:07 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 57A773A69C5 for <sipcore@ietf.org>; Tue, 31 Aug 2010 11:39:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,299,1280721600"; d="scan'208";a="235626694"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 31 Aug 2010 14:39:33 -0400
X-IronPort-AV: E=Sophos;i="4.56,299,1280721600"; d="scan'208";a="510560429"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 31 Aug 2010 14:39:33 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 31 Aug 2010 14:39:33 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Tue, 31 Aug 2010 14:36:55 -0400
Thread-Topic: [sipcore] #2: Editorial: section 2 is really confusing
Thread-Index: ActJI9mXapGgZRCSRJaqdRpzUvfdPAAF6L21
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C02@DC-US1MBEX4.global.avaya.com>
References: <294E3E61-2DFE-4427-92F0-EDBDBE2888CC@acmepacket.com> <CD5674C3CD99574EBA7432465FC13C1B21FFC79BFD@DC-US1MBEX4.global.avaya.com>, <AANLkTinnYZDcy7WLq-zeik65b9Cv-Q1Ck+-TW-c9_=KQ@mail.gmail.com>
In-Reply-To: <AANLkTinnYZDcy7WLq-zeik65b9Cv-Q1Ck+-TW-c9_=KQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sipcore@ietf.org" <sipcore@ietf.org>, Hadriel Kaplan <HKaplan@acmepacket.com>
Subject: Re: [sipcore] #2: Editorial: section 2 is really confusing
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2010 18:39:08 -0000
________________________________________ From: Mary Barnes [mary.ietf.barnes@gmail.com] I'm of the mindset right now that we should resolve all the other editorial issues and see if being more precise with the current definitions doesn't help and just live with the ambiguity as we've lived with it for other terms. The important aspect is what happens with the protocol and I think it's more important to get the normative text correct. ______________________________________________ It seems to me that the definitions of "retargeting", "redirecting", etc. (with the possible exception of "diversion") are not clear and have never been clear. Up until 4244bis, this hasn't mattered. But in 4244bis these allegedly distinct operations cause different things to go on the wire, so we have to make the definitions unambiguous. Dale
- [sipcore] #2: Editorial: section 2 is really conf… sipcore issue tracker
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … DRAGE, Keith (Keith)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Mary Barnes
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … Worley, Dale R (Dale)
- Re: [sipcore] #2: Editorial: section 2 is really … Hadriel Kaplan
- Re: [sipcore] #2: Editorial: section 2 is really … DRAGE, Keith (Keith)
- Re: [sipcore] #2: Editorial: section 2 is really … marianne.mohali