Re: [savi] Which vendors have coded and which operators have deployed?
Mikael Abrahamsson <swmike@swm.pp.se> Sun, 08 May 2016 11:04 UTC
Return-Path: <swmike@swm.pp.se>
X-Original-To: savi@ietfa.amsl.com
Delivered-To: savi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B6412D144 for <savi@ietfa.amsl.com>; Sun, 8 May 2016 04:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level:
X-Spam-Status: No, score=-2.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 gpPoOSE_9sN0 for <savi@ietfa.amsl.com>; Sun, 8 May 2016 04:04:47 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF98D12D105 for <savi@ietf.org>; Sun, 8 May 2016 04:04:46 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 343C3A4; Sun, 8 May 2016 13:04:44 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1462705484; bh=Qm6lezTL7uXg9bXCt98TEcXA7Hyt1QbmCT21RlugMNo=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=gLzFGgRnbhqaPh2fYAmDXy0i7GNun7BvdXg2ul9xyFfySGWxbFQKJ5wsxcQOfz7YT H99hG4mQPFtdEEfXpDomwYRAdHYWIjVikjVmGj9SoVVqav/xWKu1ASmyH7KDVdHiiK M9fn1TSDnmZ5L46cznE9/r4h3uje13d4nC1zGYoQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 28CFBA3; Sun, 8 May 2016 13:04:44 +0200 (CEST)
Date: Sun, 08 May 2016 13:04:44 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Bingyang Liu <bjornliu@gmail.com>
In-Reply-To: <CAPLDopLw07VyYvcxMKmLULcduyd-nxXid6icQ-mPLyqLDJZUJg@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1605081251040.7599@uplift.swm.pp.se>
References: <29929BBA-5744-42FC-8C3E-AC381A91A986@senki.org> <alpine.DEB.2.02.1605071117210.7599@uplift.swm.pp.se> <CAPLDopKaqzWzuD4+kikkdzuJkJp+ME-BQU4Ny3KduH0WLh+RBw@mail.gmail.com> <alpine.DEB.2.02.1605080404520.7599@uplift.swm.pp.se> <CAPLDopLtmoG2MvDStE+o0E-WYiN+V0qmQQ-7qST8T5VbLnTETQ@mail.gmail.com> <alpine.DEB.2.02.1605080643210.7599@uplift.swm.pp.se> <CAPLDopJFjaVzmy5P4kqM6RFXsg6Re=K4VVLcC4FFPcPX8ZVhcQ@mail.gmail.com> <alpine.DEB.2.02.1605080753520.7599@uplift.swm.pp.se> <CAPLDopLw07VyYvcxMKmLULcduyd-nxXid6icQ-mPLyqLDJZUJg@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/savi/p-Tv2SI3glxfMd0VDqvDalF73FY>
Cc: SAVI Mailing List <savi@ietf.org>
Subject: Re: [savi] Which vendors have coded and which operators have deployed?
X-BeenThere: savi@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the SAVI working group at IETF <savi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savi>, <mailto:savi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/savi/>
List-Post: <mailto:savi@ietf.org>
List-Help: <mailto:savi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savi>, <mailto:savi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 May 2016 11:04:49 -0000
On Sun, 8 May 2016, Bingyang Liu wrote: > Thank you for your information! > I don't know whether the SAVI function is enabled or disabled by default. I don't know of any device that has SAVI-like functionality enabled out of the box. On all the ones I have encountered, you have to actually configure things in order to get SAVI(-like) functionality. I'm using SAVI-like because these kinds of functions (first-hop security/antispoofing) was around long before this WG was even formed. > Deploying the devices does not meaning operating the functionalities > anyway. I'm interested in how SAVI is really operated in practice. Since there are many different deployment models for last mile access, there are a lot of different ways of achieving security. Do you want to talk to an operator who is actually using the SAVI-like functionality in their devices? Or are you looking for white papers on how the vendors recommend they're used? -- Mikael Abrahamsson email: swmike@swm.pp.se
- [savi] Which vendors have coded and which operato… Barry Raveendran Greene
- Re: [savi] Which vendors have coded and which ope… Mikael Abrahamsson
- Re: [savi] Which vendors have coded and which ope… Bingyang Liu
- Re: [savi] Which vendors have coded and which ope… Mikael Abrahamsson
- Re: [savi] Which vendors have coded and which ope… Bingyang Liu
- Re: [savi] Which vendors have coded and which ope… Jun Bi
- Re: [savi] Which vendors have coded and which ope… Mikael Abrahamsson
- Re: [savi] Which vendors have coded and which ope… Bingyang Liu
- Re: [savi] Which vendors have coded and which ope… Mikael Abrahamsson
- Re: [savi] Which vendors have coded and which ope… Bingyang Liu
- Re: [savi] Which vendors have coded and which ope… Mikael Abrahamsson