Re: [sipcore] #35: "target parameter" is used but seems to have no meaning

Mary Barnes <mary.ietf.barnes@gmail.com> Tue, 12 October 2010 22:45 UTC

Return-Path: <mary.ietf.barnes@gmail.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 80D483A6A22 for <sipcore@core3.amsl.com>; Tue, 12 Oct 2010 15:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level:
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.102, 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 6J9iHiGS5Xzr for <sipcore@core3.amsl.com>; Tue, 12 Oct 2010 15:45:21 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 4004A3A6AB3 for <sipcore@ietf.org>; Tue, 12 Oct 2010 15:45:21 -0700 (PDT)
Received: by gxk20 with SMTP id 20so1977189gxk.31 for <sipcore@ietf.org>; Tue, 12 Oct 2010 15:46:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wo+VtgYTRx5pnrumhweQzFAZqsavm9DqtrniZoWwnp4=; b=o9ytXh/9j24jWp/nDdcFg9Jw4QGl285dD5ezkjFil4jsA4jphUrUNUuNIaln5AQLWi xunE/QmKMEHmBJHc2jVCMVrIn9N1U0RLzGotcc8UibHriQO8TfS5TKPo29kC1J7R61q0 dg3NjJk83PEBFGTYxrnwFQgZISpF4az3ehTzs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=yHfcjLSIzGlWu8hNUPvibIALIR5ijoSOHyR8DZlVfGA6kZ5kP9+pARfDQPhTcDpSyn vqStOrMyDBnsbHvdLbyRb4olc5kxt1TNloSjXXU9CUEt2iW6dPkqRCnGLC0IawV9KgFL L0tmcV50KyJiquIh8CxSok6u1bBPslk8Hl6Po=
MIME-Version: 1.0
Received: by 10.236.95.138 with SMTP id p10mr16215924yhf.87.1286923594618; Tue, 12 Oct 2010 15:46:34 -0700 (PDT)
Received: by 10.236.108.172 with HTTP; Tue, 12 Oct 2010 15:46:34 -0700 (PDT)
In-Reply-To: <061.c9aa7ca46d7e5e9f56751b89fb04d433@tools.ietf.org>
References: <061.c9aa7ca46d7e5e9f56751b89fb04d433@tools.ietf.org>
Date: Tue, 12 Oct 2010 17:46:34 -0500
Message-ID: <AANLkTik18kTub+VQ9MeX_dLhPiKSHhhMMrtGcrS7wm_1@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: sipcore issue tracker <trac@tools.ietf.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: worley@alum.mit.edu, sipcore@ietf.org
Subject: Re: [sipcore] #35: "target parameter" is used but seems to have no meaning
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, 12 Oct 2010 22:45:22 -0000

This is referring to the "hi-target" parameter defined for the
History-Info header that has values of either "rc" or "mp=x".   I can
change the references to "target" to hi-target.

Thanks,
Mary.

On Tue, Aug 31, 2010 at 1:10 PM, sipcore issue tracker
<trac@tools.ietf.org> wrote:
> #35: "target parameter" is used but seems to have no meaning
> ---------------------------------+------------------------------------------
>  Reporter:  worley@…             |       Owner:
>     Type:  defect               |      Status:  new
>  Priority:  major                |   Milestone:  milestone1
> Component:  rfc4244bis           |     Version:
>  Severity:  In WG Last Call      |    Keywords:
> ---------------------------------+------------------------------------------
>  In various places reference is made to a "target parameter" for hi-
>  entry's.  An extreme example is section 11.1, where "target" is quoted as
>  if giving the actual name of the parameter.  But there is no "target"
>  parameter per se; there are two (mutually exclusive) parameters, "rc" and
>  "mp", that are collectively called "the target parameter".  This begs for
>  better terminology.
>
> --
> Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/35>
> sipcore <http://tools.ietf.org/sipcore/>
>
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>