IETF Logo Mail Archive

[sipcore] Syntax of Feature-Caps header

Yehoshua Gev <yoshigev@gmail.com> Thu, 28 February 2019 14:23 UTC

Return-Path: <yoshigev@gmail.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C2D130E9F for <sipcore@ietfa.amsl.com>; Thu, 28 Feb 2019 06:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 AiugptxVK2Mi for <sipcore@ietfa.amsl.com>; Thu, 28 Feb 2019 06:23:40 -0800 (PST)
Received: from mail-ua1-x929.google.com (mail-ua1-x929.google.com [IPv6:2607:f8b0:4864:20::929]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88C83130EB0 for <sipcore@ietf.org>; Thu, 28 Feb 2019 06:23:40 -0800 (PST)
Received: by mail-ua1-x929.google.com with SMTP id s15so18988480uap.6 for <sipcore@ietf.org>; Thu, 28 Feb 2019 06:23:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2z0Q25XBSK4M+l/goRncH2lWUGgyWdmMdGdW+dnpBAA=; b=IXMbYfgj5yFaK3lROhXOVYhuCPaAlZ/dtBB+2jDdHquiGfm5Ug5ZRpRgr63vVZxIWG 0U/YrdblajU7BuqEP8QMIeHKwvp65/n12oKGmuUTK+Cd+B8DyepWmrJ57fENHMDnWtFg 5KbX7jtDZenPUA1pCSm/x1PWszAMvJ/upFbJDoOqhW7QpTX0Q2UNorTsN5HFqZxXNzqA +nv8jCrPHw7rV+ft7wRisAAzPRNOHM4UGiFPNLyqpv9b1dBpwHh1azaDoO2gXeeImpWg Ul5mzWSvqzrFIpDnynG98moVBUmcWlNj/me8MvIvbyPlFhV7NYUkwZT/o6PnxJk5fXSt n7rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2z0Q25XBSK4M+l/goRncH2lWUGgyWdmMdGdW+dnpBAA=; b=IpstvVzEfSRbT0TJbPz5Tb2l54/+EukAkO5HWzCcME0GGxaF6Jkl/BIX4/deDchp3R B0Lx7qj+fbCdOJcJyj0u9lfH+pwR6Qk5AAaxaF4A+Uhq87zuatmBsSeMEujXHlan3KZ1 9XuYYe82glvEHBOTn0R/ONmN9JjQkB5oqFGOey6itYYAYebpqVhWhZj0RytO9FBlIFbq p+rQW0sMl0bd0RSp8JGCepDnLiWWQKJ3FKlICKschmZuTJwSUaduF9c6iPkUBm3NJIMi Awd2+cbh8DwvJua8q6ygUXaMvvaZLUNVQmoXVoVof/9KuE3N0Rif2NnsTrnZGh/5QLHF rlrg==
X-Gm-Message-State: AHQUAua5VXMncVszbVecaE6UbhAWiyn6Kkf2kSYxFbW99k9oqliPoFj9 HE5WVkyFXtNh0vx69L7q3NJmKoO4BaJMIhNc9i8=
X-Google-Smtp-Source: AHgI3IY8oquYdHisHmUitXvdx4HqK/VL+6b3dYecbJQPbAp0+ARRlEId7OQwTkU+ZWUpNLKYRBBPeOur5gmYiIagKiA=
X-Received: by 2002:a67:2e52:: with SMTP id u79mr4576812vsu.47.1551363819260; Thu, 28 Feb 2019 06:23:39 -0800 (PST)
MIME-Version: 1.0
References: <BF2B847A-20C4-4174-86CC-CAE96A7EBEB2@ericsson.com>
In-Reply-To: <BF2B847A-20C4-4174-86CC-CAE96A7EBEB2@ericsson.com>
From: Yehoshua Gev <yoshigev@gmail.com>
Date: Thu, 28 Feb 2019 16:23:26 +0200
Message-ID: <CAF_j7ybO0v1exTuOPnrH0zV=c120qSfP2z1oJjDHpfpEr5eGbg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "sipcore@ietf.org" <sipcore@ietf.org>, eburger@standardstrack.com
Content-Type: multipart/alternative; boundary="0000000000005d4f730582f5096d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/h3yHrMZxFvh3LngtXFW0HJOCedc>
Subject: [sipcore] Syntax of Feature-Caps header
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 28 Feb 2019 14:23:50 -0000

Hi Christer,

I have a question regarding the syntax of the Feature-Caps header since
I've not managed to find any real examples of its usage.

The ABNF in RFC 6809 is defined as:
   Feature-Caps = "Feature-Caps" HCOLON fc-value
                   *(COMMA fc-value)
   fc-value     = "*" *(SEMI feature-cap)
   feature-cap       =  "+" fcap-name [EQUAL LDQUOT (fcap-value-list
                            / fcap-string-value ) RDQUOT]

Following this syntax, I guess that for sip-push the header will look like:
*   Feature-Caps: *;+sip.pns="webpush"*

One example I could find is on
https://tools.ietf.org/html/draft-ietf-sipcore-rejected-03:

*   Feature-Caps: sip.608*
Without the asterisk and the plus sign.

Which one is correct?

Due to the lack of examples, would it be possible to add an example to the
sip-push draft that includes feature capabilities and media tags
(especially that sip.pnsreg is used for both)?

Thanks,
Yehoshua

v2.23.0 | Report a Bug | By Email