# `XMediaLib.SDP.Time`
[🔗](https://github.com/Lazarus404/xmedialib/blob/main/lib/sdp/types.ex#L117)

SDP timing (`t=`) describing when the session is active.

## What problem this solves

SDP `t=` lines declare when a session is active using NTP-era timestamps.
WebRTC offers usually use `(0, 0)` for permanent sessions, but parsers still
need a typed representation of start and stop times.

Times are NTP-style seconds since 1900-01-01 UTC. `(0, 0)` means
"unspecified / permanent" and is the usual WebRTC default.

Wire form: `t=<start-time> <stop-time>`

## RFCs

* [RFC 8866](https://www.rfc-editor.org/rfc/rfc8866) pt.5.9

# `t`

```elixir
@type t() :: %XMediaLib.SDP.Time{start: non_neg_integer(), stop: non_neg_integer()}
```

Timing fields from `t=<start-time> <stop-time>`.

## Fields

* `:start` - session start time (NTP epoch seconds)
* `:stop` - session stop time (`0` often means unbounded)

---

*Consult [api-reference.md](api-reference.md) for complete listing*