Home
last modified time | relevance | path

Searched refs:MVP (Results 1 – 18 of 18) sorted by relevance

/src/crypto/openssl/doc/designs/quic-design/
H A Dquic-requirements.md25 record layer interface will be internal only for MVP and be public in a future
36 * The minimum viable product (MVP) for the next release is a pluggable record
38 does not require significant API changes. In the MVP, interoperability should be
41 * The MVP will not contain a library API for an HTTP/3 implementation (it is a
61 * For the MVP a single interop target (i.e. the server implementation list):
65 * Testing against other implementations is not a release requirement for the MVP.
127 stream QUIC easily. (MVP)
160 * QUIC performance should be comparable (in some future release - not MVP) with
183 MVP Requirements (3.2)
187 the MVP.
[all …]
H A Ddemuxer.md7 Demuxer requirements for MVP
10 These are the requirements that were identified for MVP:
21 These are optional features of the client side demuxer, not required for MVP
30 Further requirements after MVP for server support:
H A Dconnection-id-cache.md22 In MVP, a many-to-1 matching of Connection IDs per Connection object
25 When picking a non-retired connection ID for MVP, the youngest available will
53 * For MVP, it would be sufficient to only use a zero length connection ID.
54 * For MVP, a connection ID to QUIC_CONNECTION mapping need not be implemented.
55 * Post MVP, funnelling all received packets through a single socket is
58 * For MVP, the local connection ID cache need only have one element.
185 * For MVP this could just be a zero length ID.
H A Dquic-connID-retire.md6 MVP section in QUIC Route Requirements
9 MVP does most of one side of the CID management. The major outstanding items
19 MVP does not issue multiple connection CIDs, instead it uses a zero length CID.
H A Dstream-receive-buffers.md8 Receive Buffers requirements for MVP
11 These are the requirements that were identified for MVP:
32 They are not required for MVP but they are otherwise desirable:
143 Because in MVP only a single bidirectional stream to receive
H A Dquic-overview.md42 _In MVP there is a many-to-1 matching of Connection IDs to Connection
133 _For client side and MVP this module just checks that the received packet has
H A Drecord-layer.md50 pluggable record layer interface will be internal only for MVP and be public
53 * The minimum viable product (MVP) for the next release is a pluggable record
55 does not require significant API changes. In the MVP, interoperability should
62 The MVP requirements are:
64 * a pluggable record layer (not public for MVP)
84 In the MVP the METHOD approach would be private. However, once it has
90 the MVP could implement a METHOD based approach, and subsequent releases could
128 * If this option is implemented immediately in the MVP then it would avoid later
138 The METHOD based approach has been selected for MVP, with the expectation that
H A Dquic-fault-injector.md178 This is because, in MVP, it will be the client side that is under test - so the
180 MVP this will be extended in order to be able to test the server. It may be that
181 we need to do this during MVP in order to be able to observe protocol elements
H A Dtx-packetiser.md63 provided by the calling application. For MVP, this is not required to be
93 - Congestion controller (not needed for MVP).
592 MVP.)
603 purposes. (Not relevant for MVP.)
660 (Not relevant for MVP since this is only needed on the server side.)
H A Dquic-io-arch.md293 coordinated but this is not for MVP.) Thus this also is not a concern.
342 memory buffer with datagram semantics, is to be supported as part of MVP. This
/src/contrib/file/magic/Magdir/
H A Dwebassembly14 >4 lelong =1 version %#x (MVP)
/src/contrib/llvm-project/clang/lib/CodeGen/
H A DTargetInfo.h550 MVP = 0, enumerator
H A DCodeGenModule.cpp160 WebAssemblyABIKind Kind = WebAssemblyABIKind::MVP; in createTargetCodeGenInfo()
/src/crypto/openssl/doc/designs/ddd/
H A DREADME.md54 the completion of the development of the QUIC MVP (minimum viable product).
H A DREPORT.md18 Following the development of QUIC MVP, these demos have been revisited and the
/src/contrib/llvm-project/llvm/lib/Target/WebAssembly/
H A DWebAssemblyInstrSIMD.td896 // MVP select on v128 values
/src/crypto/openssl/doc/designs/quic-design/server/
H A Dquic-polling.md1609 similar to our own reactor polling in QUIC MVP.
/src/share/misc/
H A Dpci_vendors9964 1043 8056 A8R-MVP Mainboard
18132 10b4 1b88 MVP Pro 128
29928 10fc d038 GV-MVP/RX2W (1st unit)
29929 10fc d039 GV-MVP/RX2W (2nd unit)