sentence that was added. I believe
>> we just left the SHOULD as it was, and fixed this to refer to "the RFC
>> series after IETF review".
>>
>> History and github issues aside, I completely agree, a MUST would make more
>> sense here. Let’s do this.
>&
when transport segmentation is
> prefered.
> - Section 9.1.3.10 s/endpount/endpoint/
> source fragmentation of Messages. When running over IPv4, setting
> this property to true will result in a sending endpount setting the
> - Section 13: s/whith/with/
> objects allows an application to determine whith protocol(s) and
> - Section 13: s/Tranport/Transport/
> path(s) are in use. A Tranport Services system SHOULD provide a
>
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
Hi,
we’ll meet t 11:40 at the registration desk and head over to Hinodeya Ramen
Bar, 200m down O'Farrell St.
they don’t do reservations, but I checked yesterday that we will all fit there
of we arrive there before 12
AVE!
Philipp
> On 19. Jul 2023, at 07:18, Philipp S. Tiese
t 12:03 PM Colin Perkins wrote:
>
>
> On 13 Jul 2023, at 9:50, Philipp S. Tiesel wrote:
>
> >> On 12. Jul 2023, at 21:08, Gorry Fairhurst wrote:
> >>
> >> On 12/07/2023 19:41, Reese Enghardt wrote:
> >>>
> >>> On 7/12/23 11:10, Tommy P
ity of everyone!
>>
>> That would work for me, too.
>>
>> Best,
>> Reese
>
> For me: Monday seem best, then Tuesday, then Wednesday.
>
> Gorry
All three options would work for me … lets’ wait for Monday an fix Monday Lunch
if there is no v
Hi,
as it seems we have a few more TAPS in-person attendees at IETF117,
I wondered who else would be interested in a TAPS Lunch or Dinner
to celebrate the near-finish and discuss who would be interested
to work on some mappings.
Time proposals welcome.
AVE!
Philipp S. Tiesel
--
Philipp S
Hi,
I second this plan.
We should also talk briefly whether we want to have a WG meeting at IETF117 to
carry status and beginning chartering discussion into a broader audience.
> On 10. May 2023, at 22:55, Tommy Pauly
> wrote:
>
> I support using at least part of the time to triage and di
Hi,
> On 15. Mar 2023, at 22:07, Gorry Fairhurst wrote:
>
> On 15/03/2023 20:52, Michael Welzl wrote:
>> Hi !
>>
>> I would love to have an interim. These are the things that I personally
>> would like to discuss:
>> 1) what could we now do to foster deployment of this?
>> 2) is anyone really
e-mail to Karlstad University, we will process your personal
> data <https://www.kau.se/en/gdpr>.
>
> ___________________
> Taps mailing list
> Taps@ietf.org <mailto:Taps@ietf.org>
> https://www.ietf.org/mailman/listinfo/taps
>
mentation that can use multiple IP addresses, multiple
> protocols, multiple paths, and provide multiple application streams
>
> NEW:
>
> and it can provide benefit when an implementation can use multiple IP
> addresses, multiple protocols, multiple paths, and provide multiple
> application streams.
>
> ___
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
Hi,
Some of the remaining issues had already been discussed, but either did not
lead to text or the text was lost. Let me comment on these issues:
>> On 4. Mar 2020, at 15:38, Michael Welzl wrote:
>
> REMAINING UNADDRESSED COMMENTS FROM KYLE ROSE:
>
>
> 2. Terminology and Notation
>
> * The
of creating
> connections, and sending and receiving messages, is something that can
> certainly conform to a TAPS-compliant interface.
>
> If you read through draft-vvv-webtransport-overview, it largely outlines
> something that is a TAPS interface, just without
If none of the authors wants to moderate -security, I can do that.
AVE!
Philipp S. Tiesel
> On 7. Nov 2019, at 16:48, Aaron Falk wrote:
>
> Thanks, Tommy.
>
> Who will talk about -architecture & -security?
>
> --aaron
>
> On 6 Nov 2019, at 19:53, Tommy P
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
> On 4. Nov 2019, at 19:18, Kyle Rose wrote:
>
> Evidently, the transport security document.
Yes, we need to discuss next steps there. I still hope there will be some
discussion
on the list this and nex
ingapore to coordinate the action items resulting from this discussion.
AVE!
Philipp S. Tiesel
> On 24. Oct 2019, at 10:06, Magnus Westerlund
> wrote:
>
> Authors and WG,
>
> Considering the IETF last call comments by Eric Rescorla and Christian
> Huitema I
> w
; Magnus Westerlund
> --
> Cheers
>
> Magnus Westerlund
>
>
> --
> Network Architecture & Protocols, Ericsson Research
> --
> Ericsson A
ll these could include a URL a date when these pages was visited and
> contained the information you want to reference.
>
>
> Cheers
>
> Magnus Westerlund
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
> _______________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
>> From: Taps mailto:taps-boun...@ietf.org>> On Behalf
>> Of Gorry Fairhurst
>> Sent: den 23 juli 2019 20:40
>> To: Brian Trammell (IETF) mailto:i...@trammell.ch>>
>> Cc: Philipp S. Tiesel mailto:phil...@tiesel.net>>;
>> Tommy Pauly
>>
as a mandatory argument. For me, the latter is just one way to realise the
former in a language that does not support optional parameters and thus an
implementer’s choice.
>
> Thanks,
> Tommy
>
>> On Jul 23, 2019, at 10:35 AM, Philipp S. Tiesel > <mailto:phil...@tiesel
already convenience features in other places of
>> the API which should be removed if we agree on keeping the complexity to the
>> bare minimum for the core interface.
>>
>> Best regards,
>> Max
>>
>> Am 22.07.2019 19:15 schrieb Tommy Pauly > <mailto:t
l need
to reference them in the main text to make sure the API does not look overly
inconvenient. I also would like to use the profiles in one of the examples.
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
rties, i.e., we don’t need the TAPS defaults to be
TCP compatible as long as the reliable-in-order-stream profile is.
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
nlike”).
c) Do nothing and close the issue.
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
SCTP.
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
close the issue
AVE!
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
> On 2. Jul 2019, at 09:24, Michael Welzl wrote:
>
> Hi again,
>
>> On Jul 1, 2019, at 4:17 PM, Philipp S. Tiesel wrote:
>>
>>
>>
>>> On 30. Jun 2019, at 23:44, Michael Welzl wrote:
>>>
>>> Hi,
>>>
>>> S
wg/api-drafts/pull/328> and
>> https://github.com/ietf-tapswg/api-drafts/pull/327
>> <https://github.com/ietf-tapswg/api-drafts/pull/327>), I got no fire and
>> fury, but only constructive feedback.
>> So I agree with Michael that we may really have a shor
>> --aaron
>>
>> ___
>> Taps mailing list
>> Taps@ietf.org <mailto:Taps@ietf.org>
>> https://www.ietf.org/mailman/listinfo/taps
>
> ___
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.o
;> a virtual interim meeting on 2019-05-08 from 11:00 to 13:00 America/New_York.
>>
>> Agenda:
>> Topics:
>> * Framing
>> * Implementation draft -
>> https://datatracker.ietf.org/doc/draft-ietf-taps-impl/
>>
>> Information about remote participation:
>> https://ietf.webex.com/j
Hi,
just did one pass over the latest GitHub version and it looks ready to me.
I only found three small nits I opened Issues on GitHub for.
AVE!
Philipp S. Tiesel
On 25. Apr 2019, at 18:57, Aaron Falk wrote:
>
> Reminder that the working group last call for this draft ends next
Philipp S. Tiesel
--
Philipp S. Tiesel
https://philipp.tiesel.net/
signature.asc
Description: Message signed with OpenPGP
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
_____________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps
>
AVE!
Philipp S. Tiesel / phils…
--
{phils}--->---(ph...@in-panik.de)--->---(http://phils.in-panik.de),
wenn w eine aube ist dn man au dra
___
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps
AVE!
Philipp S. Tiesel / phils…
--
{phils}--->---(ph...@in-panik.de)--->---(http://phils.in-panik.de),
wenn w eine aube ist dn man au dran dre en
e API document
or may we postpone the above decisions?
- Where do we want to define the rules for naming Transport Properties and
Namespaces?
AVE!
Philipp S. Tiesel / phils…
--
{phils}--->---(ph...@in-panik.de)--->---(http://phils.in-panik.de),
wenn w eine aube ist dn
a/New_York.
>>>>>> Agenda:
>>>>>> Draft agenda:
>>>>>> 1. Partial Send/Receive
>>>>>> 2. 0-RTT
>>>>>> 3. Implementation & testing
>>>>>> Information about remote participation:
>>>
_
> Taps mailing list
> Taps@ietf.org <mailto:Taps@ietf.org <mailto:Taps@ietf.org>>
> https://www.ietf.org/mailman/listinfo/taps
> <https://www.ietf.org/mailman/listinfo/taps>
>
> ___
> Taps mailing list
> Taps
the namespace for RFCs.
Is this a good starting point?
Am I missing some important attribute candidates?
AVE!
Philipp S. Tiesel / phils…
> On 6. Aug 2018, at 11:44, Gorry Fairhurst wrote:
>
>
> I quite like the idea of trying to design a simple registry format. If it
> loo
g the lines of 'ready to publish'
> are also welcome.
>
> WGLC will conclude in two weeks on May 24, 2018.
>
> --aaron (for the chairs)
>
> ___
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listin
verhead in the
other cases.
AVE!
Philipp S. Tiesel / phils…
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
to an active discussion here and in Singapore and hope
that we find a way to push Socket Intents forward.
AVE!
Philipp S. Tiesel / phils…
> Begin forwarded message:
>
> A new version of I-D, draft-tiesel-taps-socketintents-01.txt
> has been successfully submitted by Philipp S
We’l like some time (~15-20min) to discuss our soon-to-be-submitted update to
draft-tiesel-taps-socketintents.
Details and questions i would like to discuss will follow with the update.
AVE!
Philipp S. Tiesel / phils…
> On 23. Oct 2017, at 17:22, Aaron Falk wrote:
>
> Please
2 to 5min for discussion how to proceed
with both drafts).
The Policy discussion following that might take some time…
The third draft is expected tomorrow or on Monday and I think it does not
really need separate discussing in Prague.
It is mainly context for the socket intents draft and contai
t
> Date: 27. June 2017 at 20:29:51 GMT+2
> To: "Philipp Tiesel" , "Theresa Enghardt"
> , "Philipp S. Tiesel"
>
>
> A new version of I-D, draft-tiesel-taps-communitgrany-00.txt
> has been successfully submitted by Philipp S. Tiesel and posted
;> On Jun 26, 2017, at 5:37 PM, Philipp S. Tiesel > <mailto:ph...@in-panik.de>> wrote:
>>
>> Hi Michael,
>> Hi Stein,
>>
>> I also read through the draft (now more than once) and have some questions
>> and comments.
>> I hope not to op
take - do I have to think
this something like a sockaddr_t or as a host / service pair? The latter is
much more useful for automation.
AVE!
Philipp S. Tiesel / phils…
> On 20. Jun 2017, at 15:21, Michael Welzl wrote:
>
> Dear group,
>
> We just updated the minset docum
While explicit intents are a great way to avoid ossification, I would also
>> argue that we should minimize the surface of the intents in order to reduce
>> the complexity for application writers. Do you think that some of these
>> intent properties can also be infe
algorithms in order to have their applications working.
Therefore, I prefer exposing more Intents and making them optional over relying
on being able to infer them.
AVE!
Philipp S. Tiesel / phils…
--
{phils}--->---(ph...@in-panik.de)--->---(http://phils.in-panik.de),
wenn w e
.
I am looking forward to the discussion, here and in Prague.
AVE!
Philipp S. Tiesel / phils…
___
Taps mailing list
Taps@ietf.org
https://www.ietf.org/mailman/listinfo/taps
49 matches
Mail list logo
