Re: [i2rs] Kathleen Moriarty's Discuss on draft-ietf-i2rs-protocol-security-requirements-07: (with DISCUSS and COMMENT)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 18 August 2016 13:06 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F4112DDEF; Thu, 18 Aug 2016 06:06:17 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 ZwOAjbzFc7Wb; Thu, 18 Aug 2016 06:06:15 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::22f]) (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 2D07D12DDE2; Thu, 18 Aug 2016 06:06:03 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id 97so26633633uav.3; Thu, 18 Aug 2016 06:06:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5kMVXY9V5FTBE7tO/zn6AiMD7QGtEny5uCfogk3KOG8=; b=pVF2bF3vTe3jBCTlQprmRYEwKy9JhVStGHYcAGbvmX1mQ9wfP37go1+SvFuYDmaGAX MaBDCeYSDUDnP/uJZOy/6wCSg3vbMgvahlGobwr0Jwpv/azIW3RGk/cevcgaGs/JwC3b 0423Ljyhd8ZLyqiSP5RzqXZQj3XH5S3dAQaQ/xHQAPE+1yutRT7bj0FN6Nic1/kA3pOH 3nAfMz2KYd2q5WipN3XrOIaGZWLjKPWwejnkoEdoT9Lpe9iK4Nbsk9g7Oukw3GQM+YK2 n77nDObloJnyfwEqTYCHY6w0M4Wbh2tGnGy0diarC0SfrGVyUw0fueuCSewthfGxKYrZ ssAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5kMVXY9V5FTBE7tO/zn6AiMD7QGtEny5uCfogk3KOG8=; b=TtQvLWf5lAvlx5sQU3UJp8SePeeHuBQknrynrzyT48XhgvQUjguk0of1bojP896JA+ s03RdnD273lM060SM5Q7WPiWluU3EDy0vf1e+wRSXGdqs0pp3c83t+lUI4y+ZKh3E3oR 6VNx51qqww2s3gQWiWOiMrdzbFL+0aUtNLhIECuwDSNPTooVi5eaTHSw8p20KzU7SlMy CEVRL6q7k518iyyUL6+FNSLRqVAx4IJvSdhB+Yxrh5wOrGxTIRSbyNYEeGPfDpq7WG/c aFL15nq43111yjrVo51V0PlPTbySm4AdKM3aHfY1o37ZiwI9x2V27UOwlOQQsiPiZsDp ovQA==
X-Gm-Message-State: AEkoouuWKjlCikDZaUEEaxPxBk1/+NM4sywrf7n9PxVjK7IVTVbb56yEkhAZHnmkvbDnnFkxnksr6l/GtuUhxQ==
X-Received: by 10.176.83.98 with SMTP id y31mr1035241uay.88.1471525562207; Thu, 18 Aug 2016 06:06:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.1.228 with HTTP; Thu, 18 Aug 2016 06:06:01 -0700 (PDT)
In-Reply-To: <051301d1f950$7739c670$65ad5350$@ndzh.com>
References: <147146974235.23784.4389421535496134619.idtracker@ietfa.amsl.com> <013b01d1f8ee$31fa09b0$95ee1d10$@ndzh.com> <20160818073203.GA4338@elstar.local> <04b501d1f949$116c63e0$34452ba0$@ndzh.com> <20160818121405.GA5282@elstar.local> <051301d1f950$7739c670$65ad5350$@ndzh.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 18 Aug 2016 09:06:01 -0400
Message-ID: <CAHbuEH6h5M8uWr7j3UpjTgZPaGC0vCVB1a2_x1XR0PUfU_byRQ@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/i2rs/X1l78I0pGaUSj7I9lvbItngitYA>
Cc: i2rs@ietf.org, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, i2rs-chairs@ietf.org, The IESG <iesg@ietf.org>, Jeffrey Haas <jhaas@pfrc.org>, draft-ietf-i2rs-protocol-security-requirements@ietf.org
Subject: Re: [i2rs] Kathleen Moriarty's Discuss on draft-ietf-i2rs-protocol-security-requirements-07: (with DISCUSS and COMMENT)
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 13:06:17 -0000

On Thu, Aug 18, 2016 at 9:00 AM, Susan Hares <shares@ndzh.com> wrote:
> Juergen:
>
> Yes, we seem to disagree on the value of making it hardwired in the model.
> For me, the value is a common understanding of deployment distribution such
> as the route-views.   Since the operators argued strongly for this point, I
> think the best idea is to get it working in code and then see if the
> deployment matches the requests.

This sounds like more of an experiment, doesn't it?

Thanks,
Kathleen

>
> Sue
>
> -----Original Message-----
> From: i2rs [mailto:i2rs-bounces@ietf.org] On Behalf Of Juergen Schoenwaelder
> Sent: Thursday, August 18, 2016 8:14 AM
> To: Susan Hares
> Cc: i2rs@ietf.org; i2rs-chairs@ietf.org; 'Kathleen Moriarty'; 'The IESG';
> jhaas@pfrc.org; draft-ietf-i2rs-protocol-security-requirements@ietf.org
> Subject: Re: [i2rs] Kathleen Moriarty's Discuss on
> draft-ietf-i2rs-protocol-security-requirements-07: (with DISCUSS and
> COMMENT)
>
> Sue,
>
> I still do not see why the 'mode of exposure' of data benefits from being
> hard-wired in the data model. For me, it is a situational and deployment
> specific question. But I shut up here since I aired this concern before (and
> we simply seem to disagree).
>
> /js
>
> On Thu, Aug 18, 2016 at 08:07:18AM -0400, Susan Hares wrote:
>> Juergen:
>>
>> My example is the looking glass servers for the BGP route views
>> project
>> (http://www.routeviews.org/) or a route indicating the presence of a
>> web-server that is public.   For the BGP I2RS route, a yang model could
>> replace the looking glass function, and provide events for these looking
>> glass functions.    For the web-server route,  an event be sent when that
>> one route is added.
>>
>> Sue
>>
>>
>> -----Original Message-----
>> From: Juergen Schoenwaelder
>> [mailto:j.schoenwaelder@jacobs-university.de]
>> Sent: Thursday, August 18, 2016 3:32 AM
>> To: Susan Hares
>> Cc: 'Kathleen Moriarty'; 'The IESG'; jhaas@pfrc.org; i2rs@ietf.org;
>> i2rs-chairs@ietf.org;
>> draft-ietf-i2rs-protocol-security-requirements@ietf.org
>> Subject: Re: [i2rs] Kathleen Moriarty's Discuss on
>> draft-ietf-i2rs-protocol-security-requirements-07: (with DISCUSS and
>> COMMENT)
>>
>> On Wed, Aug 17, 2016 at 09:16:48PM -0400, Susan Hares wrote:
>> > --------------------------------------------------------------------
>> > --
>> > COMMENT:
>> > --------------------------------------------------------------------
>> > --
>> >
>> > > Section 3:
>> > > Can you clarify the second to last sentence?  Do you mean there
>> > > are
>> sections that indicate an insecure transport should be used?
>> > >   I2RS allows the use of an
>> > >  insecure transport for portions of data models that clearly
>> > > indicate  insecure transport.
>> >
>> > >  Perhaps:
>> > >  I2RS allows the use of an
>> > >  insecure transport for portions of data models that clearly
>> > > indicate the use of an  insecure transport.
>>
>> I still wonder how a data model writer can reasonably decide whether a
>> piece of information can be shipped safely over an insecure transport
>> since this decision often depends on the specifics of a deployment
> situation.
>>
>> /js
>>
>> PS: I hope we do not end up with defining data multiple times (once
>>     for insecure transport and once for secured transports).
>>
>> --
>> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
>> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
>> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>>
>> _______________________________________________
>> i2rs mailing list
>> i2rs@ietf.org
>> https://www.ietf.org/mailman/listinfo/i2rs
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>



-- 

Best regards,
Kathleen